[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:                |     Focuses:  docs
--------------------------+---------------------
Changes (by coffee2code):

 * keywords:  dev-feedback =>


Comment:

 @costdev: Sorry, I was waiting on making and testing parser and !DevHub
 fixes to accommodate the code fence syntax. As I just noted in my prior
 comment, that support has been added and the issues reported here are no
 longer an issue in the Code Reference.

 However, as I also noted, the use of code fences in inline docs is new.
 #core-docs people should determine if its usage should be added to the
 documentation standard or if the existing handful of code fence syntax
 usage should be removed from core. Again, see the last bit of my previous
 comment.

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