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

51–60 of 136 posts

Re: Every HTML Element

#52

Post by alwillis »

mg wrote: post #4

I wonder if it would be possible to do this in a way that the page shows its own source code. Similar to: https://no-gravity.github.io/html-quine/index.html Could be tricky, because non-textual elements would probably have to be taken care of individually. For example a video would probably have to show a video of its own representation in code.

This is very good: https://meiert.com/en/indices/html-elements/

Re: Every HTML Element

#54

Post by worble »

hn_acker wrote: post #50

The element says "This is a modal dialog displayed using just HTML." but that's a bit misleading because the dialog opens using JavaScript `document.getElementById('my-dialog').showModal()` in the onclick attribute of the relevant button.

Which is strange because you absolutely can open dialogs without javascript with the popover attribute

https://developer.mozilla.org/en-US/docs/Web/API/Popover_API...

Re: Every HTML Element

#55

Post by tannhaeuser »

adzm wrote: post #25
robby1066 wrote: post #13

First I've ever heard of hgroup. Subheadings are one of those little things I've wondered about the proper semantics for a million times and always end up doing something slightly different on the fly.

hgroup is considered deprecated in HTML5 though, whatever that actually means.

Worse, it has changed content rules and semantics in backward-incompatible ways. Meaning there are pages out there that used to be valid, but aren't anymore. And since HTML spills to EPub specs, I recall there were EPubs or EPub spec examples/test suites themselves having to change specifically, epubcheck being actually used for validation and hence directly noting this backward incompatibility.

In a nutshell, hgroup was originally criticized and rejected when W3C was still redacting HTML specs received from the loose group of browser devs and other people calling themselves "WHAT working group" because it paired headings of multiple ranks in a way that confused assistive technologies in browsers. But the first (and at the same time the last;) W3C HTML recommenndation created as unredacted WHAT WG spec snapshot under the W3C/WHATWG "memorandum of understanding" actually smuggled hgroup in. Then Steve Faulkner removed HTML outlining and the whole concept of sectioning roots that was part of Ian Hickson's vision of "HTML 5" for the longest time, but W3C never actually started a new recommendation process afterwards, and the charter for the HTML WG at W3C, Inc. has ended last year. See details at [1].

Arguably, with this change in 2023, we're now post-HTML5. But don't tell the people believing in a single "HTML 5 standard".

[1]: https://sgmljs.net/blog/blog2303.html

Re: Every HTML Element

#56

Post by sigzero »

hn_acker wrote: post #50

The element says "This is a modal dialog displayed using just HTML." but that's a bit misleading because the dialog opens using JavaScript `document.getElementById('my-dialog').showModal()` in the onclick attribute of the relevant button.

Correct, it is only modal if JavaScript is used.
Post reply on HN