[wp-trac] [WordPress Trac] #59432: Compliant with W3C coding standards

[WordPress Trac]

#59432: Compliant with W3C coding standards
-------------------------+------------------------------
 Reporter:  agypten      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:  6.3.1
 Severity:  minor        |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by dmsnell):

 > Since WordPress always use quoted attributes, this warning/notice should
 be ignored.

 I disagree on the first part, because plenty of places in WordPress expose
 various kinds of quoting, and many plugins end up breaking quoting. That
 is, we're still susceptible to dangling unquoted attribute next to the
 trailing `/`, even if it doesn't come from some specific code inside
 WordPress.

 On the second part though I agree. Though it's probably best if we don't
 intentionally produce void elements with a trailing slash, to proactively
 remove them is only going to add overhead without changing anything
 material in the rendered pages.

 @agypten an approach you might consider is looking at WordPress code that
 generates these and propose changes to those places.

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