Jeffrey muses on progressive enhancement and future-friendliness.
This is an interesting thought from Scott: using Shadow DOM in HTML web components but only as a way of providing sort-of user-agent styles:
providing some default, low-specificity styles for our slotted light-dom HTML elements while allowing them to be easily overridden.
Three great examples of HTML web components:
What I hope is that you now have the same sort of epiphany that I had when reading Jeremy Keith’s post: HTML Web Components are an HTML-first feature.
So many of the problems and challenges of working with Web Components just fall away when you ditch the shadow DOM and use them as a light wrapper for progressive enhancement.
Some lovely HTML web components—perfect for progressive enhancement!
I somehow missed this when it came out in January but Amber just pointed me to it—an interview with Chris about HTML web components, available for your huffduffing pleasure.
Naming custom elements, naming attributes, the single responsibility principle, and communicating across components.
You might want to use `display: contents` …maybe.
HTML web components for augmenting date inputs.
Don’t replace. Augment.
It’s fine to require JavaScript for read/write functionality. But have you considered a read-only mode without JavaScript?