HTML web components | Adactio

An excellent look into the new trend of no-or-low-JavaScript web components, which almost operate more like HTML fragments, with graceful fallbacks to native elements. Jeremy proposes terming these "HTML Web Components", but I'm not totally sold on that.

On some of the key positives of native web components:

It’s not just that web components are portable. They’re also web standards, which means they’ll be around as long as web browsers. No framework can make that claim

On thinking about web components as ways to extend native HTML elements rather than create them from scratch:

HTML web components encourage a mindset of augmentation instead.
Instead of all-singing, all-dancing web components, it feels a lot more elegant to use web components to augment your existing markup with just enough extra behaviour.

Explore Other Notes

Newer

Breaking out of the box

Patrick Brosset covers a range of new(ish) web and browser APIs that allow PWAs to benefit from OS-level functionality to style and utilise more of the browser chrome. Specifically, the Windows …

Older

EU overlay statement

An official statement from the European Commission on accessibility "overlays" and EAA compliance. The outcome? Overlays are insufficient and potentially damaging to accessibility. Whilst they don't …

  • <!DOCTYPE html> <html> <head> <title></title> </head> <body> <p>An excellent look into the new trend of no-or-low-JavaScript web components, which almost operate more like HTML fragments, with graceful fallbacks to native elements. Jeremy proposes terming these …</p> </body> </html>
  • Murray Adcock.
Journal permalink