@jaffathecake it's more explicit, which is good and would theoretically be easier to parse except parsers cannot really on it because HTML is so forgiving and people exploiting that.
@jaffathecake because, while being much maligned in the last decade, XML got something right, and it's this part of the spec. HTML's self-closing behavior is obscure and confusing and hazardous.
Hixie should have fixed this in HTML5 to allow authors to opt in to the sane thing without going full-on XHTML (not that there's anything wrong with that; cf <https://www.nayuki.io/page/practical-guide-to-xhtml>).
@jaffathecake this is just some noob who doesn’t know how p tags work. Although in their defense, the closing of html tags is quite wildly inconsistent, with all sorts of different rules for different elements.
@jaffathecake consistency, maybe? from a mental load standpoint the idea that we should close all the tags is simpler than remembering which tags we should and shouldn't close.
Another instance where something that was meant to simplify writing code ends up making it harder.
@jaffathecake Could be react-thinking bleeding through into HTML, perhaps. Enough people have joined the industry as a "react-first" engineer (maybe a "framework-first", I don't know if other frameworks do this) that they learned All Tags Must Be Closed And All Tags Can Be Self Closing, perhaps?
@sil@jaffathecake not the only reason.
Who is old enough here lived in the XHTML age, when suddenly XML/HTML was the way to go (especially here in Italy, for an old accessibility act).
Also nowaday, when I write ye-olde plain HTML I still self close some tags because I used to do it for years.
Add comment