Web Components API/Specs Report and Alignment

[Westbrook]

Session description

The Web Components Community Group will share their 2023 report on the APIs and specs that are deserving of prioritization across implementors in 2023 going into 2023. This follows up on previous reports in 2021 and 2022. From there, we will have an open discussion on how the community group can support implementors in shipping, coming to consensus, or altering various specs in order to get them into the hands of developers and their site/application visitors in as prompt a manner as possible.

Last years discussion focused on browser parity and spec alignment. Implementor partnerships lead to x-browser support for Imperative Slotting and Constructible Stylesheets, expanded support for Form Associated Custom Elements, and progress on CSS module scripts, as well as the triumphant return of the Web Components Spring Face to Face (albiet virtual) to further flush out features like Cross-root Aria, Scoped Registries, and Declarative Shadow DOM. We look forward to what we can do in the next year as we continue to develop the relationship between implementors and web developers.

Session goal

Align implementors on high priority web component APIs for shipping in 2024

Additional session chairs (Optional)

@keithamus

IRC channel (Optional)

#webcomponents

Who can attend

Anyone may attend (Default)

Session duration

60 minutes (Default)

Other sessions where we should avoid scheduling conflicts (Optional)

No response

Estimated number of in-person attendees

Don't know (Default)

Instructions for meeting planners (Optional)

No response

Agenda, minutes, slides, etc. (Optional)

• Agenda
• Slides
• Minutes
• Calendar

[tidoust]

Had to drop the "early draft" from the agenda link. Sorry, our system cannot deal with nuances!

[keithamus]

Summary of meeting:

• @smaug---- claims Firefox is working on DSD and hopes to show progress soon.
• @rniwa explained some concerns around open issues on Scoped registries. More to follow in breakout session.
• @josepharhar suggested there is yet to be any active prototyping on Cross Root Aria in Chromium
• @justinfagnani raises concerns around CSS Slot Content Detection. @rniwa raises concerns about the syntax of the proposal; making it a combinator may not be possible, maybe it can be a pseudo class. @rniwa suggests raising this to the CSSWG would be a good first step.
• @smaug---- is curious about Declarative Custom Elements, and would like the CG to feedback on proposals. @justinfagnani claims there are multiple use cases and it would be good to do out reach on these. @rniwa agrees gathering use cases is a good next step; The precursor to Web Components - XBL - might be a good place to provide these use cases. @justinfagnani claims that Template Parts may be a good first step through the path of Declarative Custom Elements. @rniwa and @smaug---- don't consider this to be a blocker.
• @rniwa supports further discussions and more face-to-face (virtual) meetings but also raises that it might not be the issue that is leaving proposals open, and there could be work to better progress/conclude proposals. @josepharhar speaks to the process of the OpenUI community group, and how scribing + recorded resolutions help with process, although the CG is still required to take these resolutions to the WHATWG, so while not final it is valuable. @justinfagnani claims web components work used to be part of the WebApps WG, and maybe ownership and process needs clarity. @Westbrook points out that it seems to be not just process but regularity that helps other CGs make progress. The group comes to general agreement for more virtual meetings, and some discussion and requests for more structure in each meeting.

[justinfagnani]

@justinfagnani claims the WCCG used to be part of the WAWG, and maybe ownership and process needs clarity.

I said that I believe the web components work used to happen under the WebApps WG, not that WCCG was part of that WG. The WCCG didn't exist back then.

[keithamus]

Thanks, updated.