I wouldn't say hgroup is experimental. It was on the standards track and now it's being deprecated.
Show HN: A guide to all HTML5 elements and attributes
41–50 of 97 posts
Re: Show HN: A guide to all HTML5 elements and attributes
#42Good stuff. Would be even nicer if it showed information about optionally self-closing tags, which is one of the main reasons I occasionally need to look at the spec. For instance: > A p element's end tag may be omitted if the p element is immediately followed by an address, article, aside, blockquote, div, dl, fieldset, footer, form, h1, h2, h3, h4, h5, h6, header, hgroup, hr, main, nav, ol, p, pre, section, table,…
Re: Show HN: A guide to all HTML5 elements and attributes
#43That's really well laid out. Less detail than MDN, but that site can be overkill. Two small pieces of feedback. HTTPS support would be good. Also, when I scroll the list of element and then click on one, I'm taken back to the top of the list - I'd like to stay where I am.
I think a nice feature would be if the description pages linked to the relevant MDN page - for when you want more extensive information about an element. Otherwise, I love this OP. Will likely use it regularly!
They do, top right next to (the useless, ridiculous) 'share' link.
Re: Show HN: A guide to all HTML5 elements and attributes
#44Why does it want me to whitelist it in my adblocker when it claims to be free and to always be free?
It's free to you, not free to them.
Re: Show HN: A guide to all HTML5 elements and attributes
#45I really find this format super easy to read, even if there may be slight inconsistencies and nuances to reading it.
Re: Show HN: A guide to all HTML5 elements and attributes
#46Really cool. One feature request. when a description of a tag refers to another tag, then those tags should be links. For example the description for is: Defines a list item within an ordered list or unordered list . Here I should be able to click on and to get information about those tags.
Re: Show HN: A guide to all HTML5 elements and attributes
#47I believe your kbd example is incorrect. You suggest > To save, press Ctrl + S . But the spec (both W3C and WHATWG) suggests that individual keys should be nested inside an outer tag: "When the kbd element is nested inside another kbd element, it represents an actual key or other single unit of input as appropriate for the input mechanism." Thus, the example should be: > To save, press Ctrl + S . Cite: https://w3c.gi…
It remained more or less the same through HTML 4.01: "Indicates text to be entered by the user."
The notion of using nested kbd tags to indicate literal keys appears to have been introduced by WHATWG when working on HTML5.
...I'll dig into this more and actually write a blog post about it. I'm this close to relaunching a proper blog.
Re: Show HN: A guide to all HTML5 elements and attributes
#48I believe your kbd example is incorrect. You suggest > To save, press Ctrl + S . But the spec (both W3C and WHATWG) suggests that individual keys should be nested inside an outer tag: "When the kbd element is nested inside another kbd element, it represents an actual key or other single unit of input as appropriate for the input mechanism." Thus, the example should be: > To save, press Ctrl + S . Cite: https://w3c.gi…
already exists :/?I'd think a website like this should be opinionated and remove the tags that are useless or should be deprecated in a web 5.0 world (huhu)
(great website btw)
Re: Show HN: A guide to all HTML5 elements and attributes
#49Call me paranoid, but I see this diverging from actual specs, then people googling for "html reference" finding it and thinking it is something official. The result would be another W3Schools disaster[1].
In my opinion, the official W3 specification pages are not that bad, and alternatively there's the simpler MDN with strong community support (thus lower risk of deprecation).