Re: [WICG/webcomponents] 2024 TPAC planning (Issue #1065)

The couple of things I can think of based on our recent meetings:

- Are implementors outside of Chromium still aligned on https://github.com/WICG/webcomponents/blob/gh-pages/proposals/reference-target-explainer.md? It's been evolving a bit, and the initial implementation from the Microsoft team is coming close to done. It would be great to reconfirm that other implementors are onboard and what (if any) support the community can lend in furthering the **_absolutely most important_** issue we face an custom element authors.
- We're discussing a couple of CSS selector additions that it would be good to make sure implementors are aligned on:
  - The ability to match `:host:has(...)`, on top of the great work WebKit has done in support of `:host(:has(...))`: https://github.com/w3c/csswg-drafts/issues/10693
  - `:has-slotted(...)`: https://github.com/w3c/csswg-drafts/pull/10586
- And while thinking about CSS, getting insight into any blockers that implementors are seeing around bringing `... with { type: 'css' }` to the JS module system would be nice as well.

Baring any bad news, they should all fit as smaller conversations in a larger window, rather than needing their own individual blocks. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/1065#issuecomment-2285146375
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/1065/2285146375@github.com>