Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #36735, comment 24


Ignore:
Timestamp:
07/16/2016 02:50:17 PM (8 years ago)
Author:
joemcgill
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36735, comment 24

    initial v1  
    22> @joemcgill thanks for the quick fix here, I was looking at this ticket today with @afineman and wondering if in `wp.html.string` we should be inserting as the comment calls it 'empty attribute notation' for any attribute?
    33
    4 This is a good question. Looking back through the history here, it seems like the current behavior was introduced in [22567], but it's not clear why @koop added this "empty attribute notation" check. Looking at the W3C draft spec, the only valid use case for that style that I could come up with is this section on [boolean attributes](http://w3c.github.io/html/infrastructure.html#sec-boolean-attributes). Ex:
     4This is a good question. Looking back through the history here, it seems like the current behavior was introduced in [22567], but it's not clear why @koop added this "empty attribute notation" check. Looking at the W3C draft spec, the only valid use case for that style that I could come up with is this section on [http://w3c.github.io/html/infrastructure.html#sec-boolean-attributes boolean attributes]. Ex:
    55
    66{{{