- From: Westbrook Johnson <notifications@github.com>
- Date: Mon, 18 Mar 2024 12:33:09 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <WICG/webcomponents/issues/1050/2004761735@github.com>
@annevk, I reached out with a pretty long runway to get availability and didn't have agenda info at the time, but we'll have a structure to the conversation. However, I do agree with @mfreed7 that open discussion can be a very powerful part of developing for the future the way that has been brought up by several implementors (including yourself) as recently as January's face-to-face. Not to set anything in stone, but the [Web Components Community Group](https://github.com/w3c/webcomponents-cg) has been meeting on an almost weekly basis to address the [action items](https://github.com/WICG/webcomponents/issues/1031#issuecomment-1885640485) from our last face-to-face. The top three or four items for discussion persist: 1. Scoped Element Registries - we're working on getting in-person reportable feedback and findings from the Chromium prototype to help clarify next steps for all implementors 2. Cross Root ARIA - a progress report on @behowell's proposal and practical feedback from teams at WebKit and Firefox as to whether it's something we can support getting a contribution to their implementations of 3. Open Stylable Shadow Roots - use cases! - proposals - demos - scoping, rescoping, dividing into one or more paths forward 4. Declarative Custom Elements - it's time, and while it's a thorny complicated concept we've been gathering lots to discuss that will benefit from in-person attention across the whole implementor community Beyond that, this would also be a great place to hopefully get insight on things like: - @tabatkins and @fantasai's position on https://github.com/w3c/csswg-drafts/issues/6867 and https://github.com/w3c/csswg-drafts/issues/5629 and https://github.com/w3c/csswg-drafts/issues/10013 - hear what implementors have been thinking about as far as specs and APIs, we'd love to have everyone join the WCCG's regular meetings but realize that's not always possible. We want to know what we as a community group can support the collection of you all in bringing to life, too. - there's also something to be said about triaging and cleaning up [this issues list](https://github.com/WICG/webcomponents/issues) as a weeded garden is most likely to grow, etc., etc., platitudes 😉 Hopefully this positions this in the "want to attend" column of your schedule in the timeframe outlined in https://www.when2meet.com/?23874110-FaIek. If not, how can we make this something that more implementors like yourself would be excited to partake in? -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/1050#issuecomment-2004761735 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/1050/2004761735@github.com>
Received on Monday, 18 March 2024 19:33:13 UTC