Re: [WICG/webcomponents] Spring 2023 "F2F" (Issue #978)

For topics, we might find the [Web Components Community Groups report from 2022](https://w3c.github.io/webcomponents-cg/2022.html) a good starting point.

When presenting this content at TPAC we focused primarily on some APIs needed for [browser parity](https://w3c.github.io/webcomponents-cg/2022.html#browser-parity), that have happily made some really great progress as far as implementation. FACE (Form-Associated Custom Elements), Constructable Style Sheets, CSS Modules, and Imperative slots have all seem massive progress in the intervening months, there may no longer be further discussion needed in these areas....

As part of the report, the community group saw a great need for closure/[alignment](https://w3c.github.io/webcomponents-cg/2022.html#spec-alignment) on specifications for Cross-root Aria, Scoped Registries, and Declarative Shadow DOM. DSD looks like it's ready to go, the team at WebKit has been putting some great work into it and it's on by default in their Tech Preview 162. Scoped Registries and Cross-root Aria have more work required. *Speaking not as the WCCG chair, but for Adobe, my employer, these two specs are of high interest and import to products/features that are shipping to users today and new products/features that will be rolling out in the coming years, if that's of any use in putting extra fuel on the fire.*

- A specification for [Cross-root Aria](https://github.com/leobalter/cross-root-aria-delegation) has been making the rounds in the AOM Working Group and has been well received by implementors of various engines in that context. It would be great to drive this forward, find any remaining holes in the idea, and push for official spec text/implementation agreement.
- For [Scoped Registries](https://w3c.github.io/webcomponents-cg/2022.html#scoped-element-registries), Chrome has issued an [Intent to Prototype](https://groups.google.com/a/chromium.org/g/blink-dev/c/um-9YjJWyEQ/m/MhKN0L7FAgAJ?pli=1). As that moves forward, it would be good to make sure we're officially in agreement around final [open questions](https://w3c.github.io/webcomponents-cg/2022.html#open-questions-14) on the specification.

Beyond those, the [various API](https://w3c.github.io/webcomponents-cg/2022.html#table-of-contents) covered in the WCCG report are all sourced from actual consumers of the web components APIs, so it may be useful to find time in a F2F to work towards closing the various "open questions" sections there in. In particular, if there are "dissenting opinions" there in that can be represented by specific implementors, it would be great to ensure that we've made time before/during/after the session to ensure those positions are fully captured and shared with the broader community.

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

Message ID: <WICG/webcomponents/issues/978/1404475603@github.com>