@leaverou These all power HTML in some way or other...

- Scoped Custom Element Registries
- Reference Target API
- elementInternals.type https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ElementInternalsType/explainer.md
- Declarative CSS Modules and the adoptedstylesheets attribute https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ShadowDOM/explainer.md
- Declarative Partial Updates https://github.com/WICG/declarative-partial-updates
- DOM Parts
- Platform based windowing/virtualization
- <tabs>

I've got lots more for CSS/JS if you get signed up for those.

Good luck with the survey!

#webComponents #webComponentsCG #webDev

@bkardell @nomster Very interesting. Shares desires with a lot of discussions that have been happening in the #webComponentsCG as of late. Definitely see the super powers this could bring to both SPA AND MPA structures sites/applications. How can the community support moving something like this forward?

#webDev #webComponents #htmlInHtml

If you like this sort of #webComponents content, or are diving into consuming/developing a myriad of new or long standing APIs available as web components, come join the conversation around making them better at https://discord.gg/kbba8cKPg9

#webComponentsCG #webDev #testTheWebForward

@zachleat @nachtfunke I'm not saying this is because I didn't get you anything for your birthday, but I'm also not saying it isn't because of that...

https://blog.westbrookjohnson.com/patterns/i-am-feeling-so-disconnected/

#webComponents #webComponentsCG #webDev #customElements #shadowDOM

@keithamus @ertian once all the kinks are worked out here, the root style sharing we chatted about last week becomes:

export class BaseClass extends HTMLElement {
constructor() {
super();
this.attachShadow({ mode: 'open' });
this.shadowRoot.adoptedStyleSheets = [...document.styleSheets];
}
}

🤯

#webComponentsCG

Super excited to see (after years of my involvement and maybe decade of @sundress’s along with MANY other passionate and patient individuals) the web getting a little more accessible: https://github.com/WebKit/WebKit/pull/39742 🥹

#webComponents #a11y #webComponentsCG #w3c

@deebloo I think there's a _nuanced_ difference between any base class being able to decorate with `@injectable` and any element opting into provide/consume via a protocol being able to work with a consumer/provider that leverages the protocol via something like `@injectable`, et al. So, it'll be exciting to hear how that might align with the work you've done and are doing!

#webComponentsCG #communityProtocols aren't "standards", but understood and shared usage patterns can be just as powerful!

Sometimes (most times?) (always?) software is better with friends...

This mornings got to hangout with some members of the #webComponentsCG and read the latest proposal for Scoped Custom Elements Registries. 🏗️

https://github.com/whatwg/html/issues/10854

Have you checked it out? Have thoughts? 👂

The community group will be meeting with implementors soon to hopefully iron out any final issues as we move towards getting the API agreed on cross browser. 🥰

@xro @mia @tabatkins I’ve had good luck in this context. Have a demo of it not working? Would love to help track down and prioritize any issues, if it was spec or browser related. I’ve been loving anchor positioning for so many things and would want to get tripped up on it further down the road!

#webComponentsCG

@intenttoship :ThisTBH: 👏 👏 👏 👏 👏

#webComponents #webComponentsCG #shadowDOM #testTheWebForward

@myobie Nice conversation! I do this a lot in my work, especially leveraging the Context Protocol from #webComponentsCG. I've been thinking about proposing a self resolving path to the protocol to better support shipping elements that aren't used with an established parent context, and might partner with other siblings/cousins/etc that could benefit from the same context. Part https://github.com/lit/lit/blob/main/packages/context/src/lib/context-root.ts (which needs to be added to the Protocol) and part default resolution.

#nativeContexts

@oldcoyote DOM parts always feel “just out of reach” at the spec level, good posts like yours outlining how they might “cover an important hole in functionality” would go a long way to getting a little extra fire under implementors.

Slottable requests are a consumption pattern the #webComponentsCG is working to codify as a Community Protocol, so if you see benefits to it, or holes in it, your experience would be highly welcome it making it more useful and helping to spread knowledge of it.

🙇‍♂️

@konnorrogers @ryantownsend @noleli I would ❤️ the heck out of an issue like that...

https://github.com/w3c/csswg-drafts/issues/new

#CSSWG #webComponentsCG #theFuture

@myobie Yes and no. There are lots of examples floating about, but not a good centralized place to find them. That's why the #webComponentsCG https://github.com/w3c/webcomponents-cg is kicking off of a "Docs and Guides" work stream. It'll be a big part of our November Meeting on Monday (listed on the calendar in the above GitHub), and async work through out the year. There's a channel for in on our Discord, https://discord.gg/Tne6E8d9, if you're interested in hoping shape/write/review content for the effort, too.

@knowler MDN accepts PRs…

I started working on https://github.com/Westbrook/axe-core-element-internals as a test bed for #ElementInternals usage for ace-core, but maybe more useful at large for these APIs. I accept PRs, too. 🤗

Also, we’re looking to reignite the push for community docs and guides for WCs in https://discord.gg/KzgaSbGc9q to clarify these sorts of things, as well.

#webComponents #shadowDOM #webComponentsCG #a11y

Have you been disappointed by the passage of time and its negative effect on webcomponents.org?

Think that #webComponent deserve a place on the internet that belies how practical and productive they are in your work?

Wanna help the #webComponentsCG bring such a thing to life?

Join us on Discord (https://discord.gg/KzgaSbGc9q) as we drive to do all this and more for the next generation of web components and web components consumers!

#webDev #w3c #readTheDocs #writeTheDocs

@jla #webComponents are great! Have you thought to join in on the conversation at the #webComponentsCG https://github.com/w3c/webcomponents-cg?tab=readme-ov-file

Also, who doesn’t love some <slot/>s?

https://dev.to/westbrook/who-doesnt-love-some-s-3de0

So we have Constructible Style Sheets https://developer.mozilla.org/en-US/docs/Web/API/CSSStyleSheet/CSSStyleSheet, should we also have Constructible HTML Documents? 🤔

E.G. where a constructed Style Sheet is shared and mutable, should there be a shared an mutable HTML primitive?

Like a lot of HTML needs to be hyper custom, but maybe the shadow DOM of oft-repeated elements like buttons or inputs? Things that rely heavily of <slot>s over templating?

#webComponentsCG #htmlModules

This seems reasonable, right #CSSWG ?

```css
custom-element::part(interactive-part) {
&:hover {
/* Please sir, can I have some styles? */
}
}
```

Feels like this was maybe an accidental side effect of specifically preventing things like:

```css
div:after {
&:hover {
/* Nothing to style here... */
}
}
```

Glad to see Tab looking for a second pass on this conversation before fully closing! 🔥

#webComponents #webComponentsCG

Now it's happening in Firefox Nightly, too, behind the `layout.css.has-slotted-selector.enabled` flag. @keithamus is a beast!! 🤘

It's this is fully shipped x-browser before Interop 2025 starts, they'll definitely pick it...if nothing else than to pad their stats!! 🤣

#webComponents #webComponentsCG #CSSWG