Re: [WICG/webcomponents] TPAC 2022 Web Components Meeting(s) (Issue #966)

Hey @mfreed7 , I can share some updates here from the WCCG at least and I think they align very well with the specs you called out.  We've been drafting a break out session to build upon our report from last year, but a with a more "focused "narrative" compared to last year.

Basically, our abstract is
> _After a brief introduction, the Web Components CG will facilitate a discussion with implementers and community members about filling browser gaps in agreed upon features, and moving forward with the next wave of top priority asks._

And the general outline we've got going so far is
> 1. **_Introduction_** - Motivations / Aspirations
> 1. **_Browser Parity_** - Specs that just need that one final implementor to obtain ubiquitous cross-browser support
>    - FACE
>    - Constructible Style Sheets
>    - CSS Modules
>    - Imperative slots
> 1. _**Spec Alignment**_ - Key specs we hope we to get cross-implementor buy-in on
>    - Aria
>    - Scoped Registries
>    - Declarative Shadow DOM
> 1. _**Appendix**_ - All the specifications (any particular order?)

It's mostly high level and focused on general alignment, but still leaves room for deep dive sessions on a particular topic too as more of a "workshop" session format if we want to host a second breakout.

We've been tracking them issues in our CG repo if anyone wants to jump in on those 👍 
- https://github.com/w3c/webcomponents-cg/issues/43

- https://github.com/w3c/webcomponents-cg/issues/48


Happy to hear your thoughts!

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/966#issuecomment-1229034656

You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/966/1229034656@github.com>