[wp-trac] [WordPress Trac] #58028: WP_HTML_Tag_Processor: Its reference in the Developer Resources is broken

[WordPress Trac]

#58028: WP_HTML_Tag_Processor: Its reference in the Developer Resources is broken
--------------------------+---------------------
 Reporter:  juanmaguitar  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.2.1
Component:  HTML API      |     Version:  6.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  docs
--------------------------+---------------------
Changes (by SergeyBiryukov):

 * keywords:   => has-patch


Comment:

 Replying to [comment:6 coffee2code]:
 > '''''However''''', whether the code fences should have been used in the
 first place is a discussion for #core-docs people. Core's
 [https://developer.wordpress.org/coding-standards/inline-documentation-
 standards/php/#description inline documentation standard] indicate that
 inline code examples should be defined using an indentation of 4 spaces.

 Ah yes, good catch. In my understanding, using a different format here
 appears to be accidental rather than intentional, so I would suggest
 updating these examples to match the format used by the rest of core, see
 [attachment:"58028.diff"].

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/58028#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform