XML-flavored self-closing elements are banished (use instead of ) God I hate that. It just doesn’t make sense. Where is the closed?
br is an empty tag and empty tags are self-closing
Fixed-Point HTML
31–33 of 33 posts
Re: Fixed-Point HTML
#32XML-flavored self-closing elements are banished (use instead of ) God I hate that. It just doesn’t make sense. Where is the closed?
br is an empty tag and empty tags are self-closing
Doesn’t make sense. What’s wrong with ? It’s a hell of a lot easier to parse than having an exception for
which is then transformed in
.
which is then transformed in
.
Re: Fixed-Point HTML
#33I’m surprised to see the highlights don’t include another common detail of the parsing algorithm that often trips people up: table rows and cells (tr/th/td) must be in one of thead/tbody/tfoot. If they’re not, they’re implicitly nested into a tbody. As in: --> Column one Column two Row one col one Row one col two --> I’ve frequently seen it cause a variety of issues with VDOM libraries, and even plain DOM libraries w…
Annother interesting table one, tr/td/th outside of a will never appear in the DOM. You can make up your own tags and they appear anywhere, but those three are magic and can only exist inside a table. Forms are also weird, if you leave off the closing tag, an implicit one is included in the DOM. However, if you have inputs further down the page, and technically outside the form, they are included in the submitted for…
Also fun stuff like you can't have a form inside a form, but if you stick a form inside a form inside a form you end up with a form in a form in the DOM anyways back when I ran into this last.