The filter checkboxes are a bit weird, for example elements (such as br and img) which are both self-closing and inline only show up if both self-closing and inline are selected, instead of one or the other. Also there are several elements such as li which are not categorized and show up even if no checkboxes are selected.
Show HN: A guide to all HTML5 elements and attributes
61–70 of 97 posts
Re: Show HN: A guide to all HTML5 elements and attributes
#62from a UX perspective i really like this. like the way it's laid out and presented - found it easy to scan. I know a lot of people big up MDN vs W3Schools and all their arguments are basically correct but i find it (mdn) really ugly and hard to read. i often find myself going to w3schools to just copy a snippet or get a 1 line description of what i need. mdn often feels more like a technical spec as opposed to a guid…
While I do find this to be the case with regard to MDN it's worth noting that in many cases they have very good practical articles: Using XMLHttpRequest, Getting Started with WebGL, Using IndexedDB, etc.
Re: Show HN: A guide to all HTML5 elements and attributes
#63Earlier quoted context omitted.
If I'm supposed to let them sell my privacy and attention, I wouldn't really call it free. Money isn't the only thing of value I can give to a website.
Free means you don't have to give them money to use it. If you use a different definition, you will often be confused.
It's the voluntary nature of the payment and whether the cost is tangible to you that determine what is free, not the currency used. Substitute "your FBI file" for your ad network profile and "compute time on your Amazon instance" for JavaScript time in your browser to make this clearer.
Re: Show HN: A guide to all HTML5 elements and attributes
#64I 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…
> Practically speaking, I would be a happier person today if I hadn't read that part of the spec, and instead persisted on in blissful ignorance of the element's intended semantics. Thanks, specs.
Hear hear! I found this hilarious and speaking to a shared feeling about some specs.
Of course, I kind of understand why these WTF elements make it into the specs. Maybe it's some stupid corner-case that the first implementor's code handled in an odd way because the code was simpler. Maybe there are other interactions that made it simpler to have this case be weird so that it would at least be consistent with that case. Most often, of course, it's because some vendor's code is a buggy mess of spaghetti code that can barely do the most basic stuff without falling over.
We've all been there... ;)
Re: Show HN: A guide to all HTML5 elements and attributes
#65Earlier quoted context omitted.
What's the point of this when 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)
> What's the point of this when already exists :/? Because keyboard input doesn't always mean code?
yes but the way you express both are usually equivalent, I don't think having too many specific tags in HTML is a good idea.
Re: Show HN: A guide to all HTML5 elements and attributes
#66really really cool. I've shared it in a facebook group for front end devs that I'm part of.
One minor issue: Your search bar doesn't look like one :) I didn't notice it until my second visit.
Re: Show HN: A guide to all HTML5 elements and attributes
#67Good 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,…
I'd rather just close the tag instead of trying to recall the specific instances of when I'm not required to close the tag.
I think the point is that you may not be expecting the P tag to auto close, in the case of things like Address.
Re: Show HN: A guide to all HTML5 elements and attributes
#68Earlier quoted context omitted.
Free means you don't have to give them money to use it. If you use a different definition, you will often be confused.
It's the voluntary nature of the payment and whether the cost is tangible to you that determine what is free, not the currency used. Substitute "your FBI file" for your ad network profile and "compute time on your Amazon instance" for JavaScript time in your browser to make this clearer.
Tell me more about this Silicon Valley place where everything is magically free?
Re: Show HN: A guide to all HTML5 elements and attributes
#69How is this updated (manually or automatically from official specs)? Call 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…
It's maintained in GitHub[1], from the same guy of cssreference.io[2].
Re: Show HN: A guide to all HTML5 elements and attributes
#70Earlier quoted context omitted.
What's the point of this when 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)
> What's the point of this when already exists :/? Because keyboard input doesn't always mean code?
> Because keyboard input doesn't always mean code?
Well speak for yourself ;)