#WebComponent
Obrigado a ti polo Lume 😊

Ao refazer o blogue, que está em três idiomas, multilanguage, sitemap e feed funcionarom juntos à primeira ✌️

Agora estou a montar com ele um blogue para escrever cousinhas de música, aviso-che quando o publicar.

Do webcomponent copia o que quigeres, para isso está!
October 28, 2026 at 5:00 PM
The power of Undefined Custom Elements
(standard available since 2016 yes! 2016)

WITHOUT using ANY JavaScript

What valid HTML do you want to write
creating a *rotating* Solar System?

Original DIV soup: learning-axis.com/snippets/5343/

No JavaScript! Web Component: jsfiddle.net/WebComponent...
October 23, 2026 at 6:49 PM
> super easy to make a simple custom element
> framework with zero tooling and a tiny amount of code

Its even easier without a framework
and do signal(like) signals
all with native code only

Then its 32 LOC: jsfiddle.net/WebComponent...

For small components I'll probably skip the signals part
October 24, 2026 at 8:09 AM
to be fair i think web components make a lot of sense when what you have are arbitrary data objects and you want to turn them into markup

i will be looking into making a webcomponent version of the sense atlas front end in the next couple weeks

but most of my stuff is Just Documents™
October 22, 2026 at 5:39 AM
Calling on all my web component GOATS to help review the new PR for the scoped custom element registries PR github.com/webcomponent...

With our powers combined, lets help push this forward
[scoped-custom-element-registry] Redesign the polyfill by sorvell · Pull Request #668 · webcomponents/polyfills
Supersedes #604. Updates the polyfill to the current registry model, including null registries, initialize(), declarative shadow roots, and registry preservation across moves, cloning, and adoption...
github.com
October 6, 2026 at 3:42 PM
Very cool new viewport #WebComponent added to NVIDIA Elements. Leverages the Invoker Commands API.

nvidia.github.io/elements/doc...
September 24, 2026 at 4:16 PM
Web Component by Sandeep Kumar Patel is a new release on Leanpub!

This book bundle is the complete reference Web Component.

Link: leanpub.com/b/webcomponent

#books #ebooks #newreleases
September 21, 2026 at 12:45 AM
And then "subscribe" is client side oauth to just write the site.standard.graph.subscription record. Drawback is you don't get the nice "unsubscribe" that sequoia's webcomponent gives you.
September 11, 2026 at 6:06 PM
Need a fully customizable back-to-top button for your site? Dont feel like coding one? I got you covered.

Last year I coded a framework agnostic web component solution. Install via npm or cdn. #100Devs #webdev #javascript #webcomponent #coding #programming #swe

github.com/DevManSam777...
GitHub - DevManSam777/back-to-top: A "back-to-top" button web component
A "back-to-top" button web component. Contribute to DevManSam777/back-to-top development by creating an account on GitHub.
github.com
August 21, 2026 at 1:37 AM
#Development #Launches
MicroLighter · A tiny, dependency-free syntax highlighter for the web ilo.im/16fglb by Dave Rupert

_____
#SyntaxHighlighter #Themes #WebComponent #ESM #Browsers #APIs #WebDev #Frontend #HTML #CSS
MicroLighter - A zero-dep syntax highlighter
No more spans!
ilo.im
August 20, 2026 at 5:11 PM
You wrote:
𝘞𝘩𝘦𝘯 𝘺𝘰𝘶 𝘱𝘶𝘵 <𝘶𝘪-𝘤𝘢𝘳𝘥> 𝘰𝘯 𝘵𝘩𝘦 𝘱𝘢𝘨𝘦, 𝘪𝘵’𝘴 𝘢𝘯 𝘏𝘛𝘔𝘓𝘜𝘯𝘬𝘯𝘰𝘸𝘯𝘌𝘭𝘦𝘮𝘦𝘯𝘵

No, Dave, it is not
log the prototype chain
See JSFiddle: jsfiddle.net/WebComponent...

Not a major difference,
but (like DSD) a UNDEFINED *IS* a HTMLelement

screenshot from my blog/JSFiddle:
dev.to/dannyengelma...
August 20, 2026 at 9:40 AM
Wow, interesting the WCA is taking off. But thats a shame, because afaik WCA doesn't support the standardized custom elements manifest schema (as defined here: github.com/webcomponent...)

But in any case, ^ thats what storybook should be supporting, because thats the standardized schema
GitHub - webcomponents/custom-elements-manifest: A file format for describing custom elements
A file format for describing custom elements. Contribute to webcomponents/custom-elements-manifest development by creating an account on GitHub.
github.com
August 18, 2026 at 10:22 AM
Hehe. @jonathanneal.bsky.social is working on some improvements to the context protocol spec actually.

I also ideated on an HTML element-based API here that I'd like to formalize.

github.com/webcomponent...
[context] element-based API · Issue #62 · webcomponents-cg/community-protocols
It would be great to have an element-based API, because it would make the context pattern not only usable with any Custom Element authoring patterns whether as function or class (Lit, solid-element...
github.com
April 22, 2025 at 8:27 PM
Some frameworks (Stencil.js, @react.dev, @svelte.dev) are 0% passing a new Custom Elements Everywhere test in the works. Fingers crossed for updates!

Other frameworks (@lit.dev, @solidjs.com, Lume, Pota) are fully passing, with @vuejs.org and @angular.dev almost there.

github.com/webcomponent...
March 5, 2025 at 10:18 PM
because the element does not have a foot JS property so therefore the foo attribute has been set and therefore the CSS works, but then you put foo={} on another custom element that does have a foo JS property and now the CSS doesn't work. Etc.

The problem and solutions: github.com/webcomponent...
New test: libraries should offer control over setting attributes vs JS properties · Issue #2352 · webcomponents/custom-elements-everywhere
Now that React 19 is coming out, it will finally have better support for Custom Elements, but it is still not as good as it could be. facebook/react#11347 Specifically see this reply to the OP: fac...
github.com
February 19, 2025 at 1:11 AM
Ideally all elements are broken into the smallest pieces, such that attributes are the initial state. As for context patterns, the solution would be to ensure those are represented by custom elements too. I wrote an idea for a community protocol on that here:

github.com/webcomponent...
December 23, 2024 at 3:37 AM
I failed to show how the dots connect. React will fail this new test:

github.com/webcomponent...

If React is updated to pass the test, className will be less inconvenient in React, is what I was getting at. We will be able to set the ‘class’ attribute instead of the ‘className’ JS property.
New test: libraries should offer control over setting attributes vs JS properties · Issue #2352 · webcomponents/custom-elements-everywhere
Now that React 19 is coming out, it will finally have better support for Custom Elements, but it is still not as good as it could be. facebook/react#11347 Specifically see this reply to the OP: fac...
github.com
December 16, 2024 at 2:11 AM
I wrote a todo for this for custom-elements-everywhere, which includes some more details:

github.com/webcomponent...
New test: libraries should offer control over setting attributes vs JS properties · Issue #2352 · webcomponents/custom-elements-everywhere
Now that React 19 is coming out, it will finally have better support for Custom Elements, but it is still not as good as it could be. facebook/react#11347 Specifically see this reply to the OP: fac...
github.com
December 15, 2024 at 10:53 PM
Good article on #WebComponents by Chander Ramesh. I know people say don't make everything a Web Component... but I make everything a Web Component lol #webStandards #webDevelopment #react
c5r.medium.com/webcomponent...
WebComponents Are (a Part of) the Future
There’s been a big brouhaha about whether Web Components have lived up to their promise. Can they replace React? Definitely not. But they…
c5r.medium.com
November 30, 2024 at 12:29 PM
Nice!!

Is there webcomponent manifest support, from wc-toolkit?

Are decorators tc39 decorators (🤞) or the old stage2 experimental decorators that we will never ever be free of (😡)?
January 13, 2026 at 7:12 AM
Ugh some webcomponent helper I earmarked sometime this past month or three which is lost, lost in the noise to me here.
December 8, 2025 at 10:15 PM
I keep wishing we could get some better WebComponent advocacy. But there's this disconnect, the missing middle between:
"here's how to get started, yes you can!" and
"GitHub YouTube Google Salesforce Adobe all use webcomponents"

The culture needs more visible bases/beachheads.
September 29, 2025 at 6:22 PM
Different take than I'd imagined but 10p% have been dreaming of a context system for web components! And here is a spec, first thing I run into when joining! So good! github.com/webcomponent...
github.com
April 16, 2025 at 7:32 PM
This #webcomponent weird-fantasy is actually somewhat unweird by compare for not replying on anything like Filesystem Access Handles / OPFS nor git nor OCI nor btrfs nor 9p.

(Encode the data as data plz plz plz. Then project it onto the page as page data.)
February 25, 2025 at 12:08 AM
But of a strong ask coming so right off the bat, but uh wonder how well it can #webcomponent -ize.

3d webcomponents are a gateway back to a vrml again. Def taking that portal.
Threlte 8 is Here! 🤗

Six months in the making, Threlte 8 redefines performance, flexibility, and developer experience for 3D web graphics using Svelte. It’s our biggest leap yet, powered by Svelte 5, exciting updates from Three.js, and tons of community input.

1/9
January 21, 2025 at 8:40 PM