HTML5 Doctor is a group site explaining HTML5 elements and APIs, with articles on semantics, video, and server-sent events.
Commenters recommend it as a good resource for the correct use of semantic HTML5 elements, and one calls its element index a favourite.
You're looking for "<style scoped>", which is in Firefox, used to be in Chrome, but was eventually removed in favor of Shadow DOM.
http://html5doctor.com/the-scoped-attribute/
http://caniuse.com/#feat=style-scoped
https://groups.google.com/a/chromium.org/forum/#!searchin/blink-dev/scoped/blink-dev/R1x18ZLS5qQ/Bjuh_cENhlQJ
I think the main reason webcomponents won out over scoped styles is because usually once you need to scope your styles, you find you also need to scope your querySelector calls, and your DOM traversals, and your IDs....and pretty soon you have shadow DOM. It's unlikely that you need style namespacing if you're just a single dev working on a static page, and it's unlikely that you won't need JS & DOM scoping if your product grows beyond that.
Kinda. WHATWG (who do the actual work on HTML) have dropped the version number and made HTML a living standard: https://html.spec.whatwg.org/multipage/
See also the FAQ: https://wiki.whatwg.org/wiki/FAQ#What_does_.22Living_Standard.22_mean.3F
And this quote by Hixie: "You know what will be around ten years from now by looking at what is implemented in two browsers today. If it’s implemented in two browsers today, I can almost guarantee it’ll still be around in ten years. If it’s not, all bets are off. This has nothing to do with “living standard” vs. versioned specs, though. HTML4 has all kinds of features that aren’t in HTML anymore — for example, <object declare> and <a coords>." (http://html5doctor.com/interview-with-ian-hickson-html-editor/)
> Take headings, for example: in component-based development, I often don't know (and shouldn't care) what level a heading is in my reusable widget, but I am forced to choose regardless.
We could have used <h1>s everywhere with Document Outline:
<body> <h1>top level heading (parent sectioning element is body)</h1> <section> <h1>2nd level heading (nested within one sectioning element)</h1> ... </section> </body> Unfortunately, this was never implemented in browsers and was removed in HTML 5.1.
https://html5doctor.com/computer-says-no-to-html5-document-outline/
I feel like this sentiment has been bubbling under the surface of my thought process every time I open up my editor. I've never taken the time to scrutinize that feeling though, too busy stressing over the details of whatever I'm making.
Perhaps only tangentially related, but our workflows are significantly related to the technologies we use, right? Ian Hickson in an interview [0]
"The Web technology stack is a complete mess. The problem is: what would you replace it with?"
[0]http://html5doctor.com/interview-with-ian-hickson-html-editor/
> A heading is a line of text providing a title for a section.
Which is exactly what <header> is trying to be.
> …introductory content for its nearest ancestor sectioning content or sectioning root element. A header typically contains a group of introductory or navigational aids.
> When the nearest ancestor sectioning content or sectioning root element is the body element, then it applies to the whole page.
Source: http://html5doctor.com/the-header-element/ (quoted from the actual spec)
>There is probably some HTML5 history API way to do it that lets me have back and forward without saving every history entry, I'll look into it.
Do you mean the Back & Forward buttons in the browser?
If you can go back/forward to different states, why wouldn't those show up as history entries? I don't think you can decouple the displayed "history" drop-down list from the behavior of the back/forward buttons (for reasons that are probably obvious).
http://html5doctor.com/history-api/