I decided not to resurrect #114711: False positive: use <br /> instead of <br>, but I can if someone wants to call this a duplicate.
XHTML is dead, long live HTML(5). I should be allowed to use <br> all I want.
I decided not to resurrect #114711: False positive: use <br /> instead of <br>, but I can if someone wants to call this a duplicate.
XHTML is dead, long live HTML(5). I should be allowed to use <br> all I want.
Comments
Comment #1
douggreen commentedIf Drupal doesn't care about <br>, please link the issue or docs. AFAICT, core now exclusively uses <br/>.
Comment #2
tim.plunketthttp://dev.w3.org/html5/spec-author-view/syntax.html#syntax-start-tag
br is a void element. It *may* be self-closing, but it doesn't need to be.
http://drupal.org/node/223584 just says "Create good HTML/markup".
Valid markup should not be flagged as bad markup.
Comment #3
tim.plunkettAlso,
grep -nr "<br>" * | wc -lshows 11 uses of br.Comment #4
douggreen commentedLook closer, those 11 uses aren't real examples.
I'll need stronger direction from the Drupal community to remove this. Please get a few more people to enter the discussion or if core removes all of the <br/> in Drupal 8.x ???
Comment #5
tim.plunkettThe point is that
<br>is valid. I'm not suggesting that the rule be changed to outlaw<br />. We can do that after #1388926: Remove all references to "self-closing" void elements in core is discussed more.But in the meantime, the rule should be commented out or removed.
Comment #6
jbrauer commentedWith that issue closed and http://stackoverflow.com/questions/1946426/html-5-is-it-br-br-or-br as support this should be done IMO.
Comment #7
douggreen commentedI give in, this was only a minor warning, and regardless of it it is dead now or if it will be dead soon, it's meaningless, so fixed in http://drupalcode.org/project/coder.git/commit/bdb009ba2bbb5a15498c8e471....