Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Every HTML Element

iamwillwang.com

Post reply on HN
Print view View original

121–130 of 136 posts

Re: Every HTML Element

#121

Post by dmsnell »

thiht wrote: post #100
assimpleaspossi wrote: post #59

>>Ah, now there's some breathing room, thanks to . That's XHTML which is XML. HTML does not use and does not need a closing slash and never has in any HTML specification. https://html.spec.whatwg.org/dev/text-level-semantics.html#t...

I hate that XHTML went away. HTML parsing is terrible

The story of XHTML is instructive to the field of software design. There are plenty of good resources on the web if you search why did XHTML fail?

HTML parsing at least is deterministic and fully specified, whereas XHTML, as an XML, leaves a number of syntax errors up to the parser and undefined.

  Conforming software may detect and report an error and may recover from it.
While fatal errors should cause all parser to reject a document outright, this also leaves the end-user without any recovery of the information they care about. So XHTML leaves readers at a loss while failing to eliminating parsing ambiguity and undefined behavior.

Interestingly, it’s possible to encode an invalid DOM with XHTML while it’s impossible to do so in HTML. That means that XML/XHTML has given up the possibility of invalid syntax (by acting like it doesn’t exist) for the sake of inviting invalid semantics.

Re: Every HTML Element

#122

Post by thiht »

dmsnell wrote: post #121
thiht wrote: post #100

Earlier quoted context omitted.

I hate that XHTML went away. HTML parsing is terrible

The story of XHTML is instructive to the field of software design. There are plenty of good resources on the web if you search why did XHTML fail ? HTML parsing at least is deterministic and fully specified , whereas XHTML, as an XML, leaves a number of syntax errors up to the parser and undefined. Conforming software may detect and report an error and may recover from it. While fatal errors should cause all parser t…

Interesting perspective, it makes me miss XHTML wayyy less. I was under the impression that XHTML (XML) was better specified and had less weirdness. I know HTML is now better specified but some of the things inherited from HTML 4 and before make no sense to me (optional closing times SOMETIMES, optional stuff everywhere).

Re: Every HTML Element

#124

Post by mock-possum »

rat9988 wrote: post #115
worble wrote: post #103

Earlier quoted context omitted.

Apologies, for some reason I was convinced you could get a proper modal using the popover api but you're right, it's not a proper modal.

Funny, when reading this sentence, it felt like an LLM that was hallucinating and apologizes when told.

I wouldn’t expect an LLM to use a phrase like “for some reason I was convinced,”

Re: Every HTML Element

#126

Post by soheil »

rav wrote: post #107

No love for the tag? "The HTML element renders everything following the start tag as raw text, ignoring any following HTML. There is no closing tag, since everything after it is considered raw text." - it's my favorite obscure deprecated HTML tag.

same as <pre no?

Re: Every HTML Element

#127

Post by assimpleaspossi »

rav wrote: post #107

No love for the tag? "The HTML element renders everything following the start tag as raw text, ignoring any following HTML. There is no closing tag, since everything after it is considered raw text." - it's my favorite obscure deprecated HTML tag.

It's not deprecated. It's obsolete and totally removed from the HTML standard since HTML4.

Re: Every HTML Element

#129

Post by assimpleaspossi »

dmsnell wrote: post #120
Neuronaut wrote: post #113

Earlier quoted context omitted.

The HTML Tags Memory Test [0] game refers to 114 tags. Your link got 113. I wonder what's missing? [0]: https://codepen.io/plfstr/full/zYqQeRw

The memory test is missing some deprecated and non-conforming elements. The HTML spec doesn’t have a single comprehensive list either, so it can be a little tricky to define or name “all” of the elements. For example, there are elements like nextid or isindex which don’t have element definitions but which appear in the parsing rules for legacy compatibility. These are necessary to avoid certain security issues, but t…

https://html.spec.whatwg.org/dev/obsolete.html

Re: Every HTML Element

#130

Post by jy14898 »

assimpleaspossi wrote: post #128
monroewalker wrote: post #123

It’d be cool to have a gutter on the left with the html tag that appears for that line

Don't know which tag you are talking about but gutters are CSS, not HTML. If you want a gutter, add one with CSS.

They're talking about the post itself and its structure
Post reply on HN