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.
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.
It would be much harder for a 15-year-old today to View Source and understand the code structure that built the website they’re on. Every site is layered with analytics, code snippets, javascript plugins, CMS data, and more.
This is why the simplicity of HTML and CSS now feels like a radical act. To build a website with just these tools is a small protest against platform capitalism: a way to assert sustainability, independence, longevity.
Some lovely HTML web components—perfect for progressive enhancement!
As a self-initiated learner, being able to view source brought to mind the experience of a slow walk through someone else’s map.
This ability to “observe” software makes HTML special to work with.
Naming custom elements, naming attributes, the single responsibility principle, and communicating across components.
Mobile Safari doesn’t support the min and max attributes on date inputs.
HTML web components for augmenting date inputs.
The `details` element is like the TL;DR of markup.
Better UX through better HTML: inputmode, enterkeyhint, and autocomplete.