Yeah - it seems like there’s frequently a desire to punch a hole through the shadow dom to allow customizations. Lots of effort put in to allow that in some ways.

We just haven’t wanted to actually do that for our use cases yet haha

So you can mess up the parent’s metadata if you’re not careful; gotta do stuff like Object.hasOwn() checks.

github.com/tc39/proposa...

2/2

Just bought! (Yesterday actually, but that’s ok)

Looking forward to getting to it!

I’m too much of a boomer to even be aware that TikTok doesn’t allow that.

Fun.

Stream in HTML that contains custom elements that automatically upgrade?

Is this built-in client side hydration? 🤔🤔🤔😆

This video with the code sample above you while you’re talking is good. I personally struggle if it’s just a person talking

Also, a link to go learn more / go more in depth / go read the spec PR / etc would be nice, and would maybe drive organic traffic to a Mozilla page you make for this too.

I’ll give you 145 for it

I learned a lot. I was able to provide input on things. I’m excited to get even more involved.

Put it in the spec asap! 😆

If they’ve moved to an iframe!

Been looking forward to playing around with the combo box stuff since we talked about it in last week’s openui meeting

Nothing like the announcer curse

Perhaps at TPAC?

I’ve been following that (and my team is very interested in this proposal);

Would enjoy working to understand your team’s hesitations, especially given Mason’s last comment and all the research + collaboration with accessibility experts there has been on this.

❤️

Jake you’re not supposed to critically look at these; just hype and boost.

(Thanks for catching that, we’ll get it fixed up!)

Just finished it. Very nice write up, thanks for the work on this