-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TPAC Bi-Weekly Preparation Sessions #98
Comments
Session no. 1 happened on 19 July at 11:30am ET. Notes are available here. Action Items
|
Join us for the next session by sharing your availability, here. |
TPAC Prep no. 2 is in the books! Thanks everyone for joining. 🙇🏼 Take a look at the notes here. Action Items:
Chat hidden within...You
|
So I am not super well versed on the current status of all of these, but I pulled the full list of items from our 2022 report which was when we last had a full list of these and tried to apply my understanding of current status to each of them, with some liberty taken to also try and use this as latest and greatest "state of" reference. On going
My thought was that anything with statuses ⚙️ , 💡 , Shipped
|
@thescientist13 with so many things covered in this table it may be more productive to start a Discussion where each of the APIs could be individual responses that then can have their own threads each? I've definitely got some updates on various things, but don't know how to share that data based on this structure. |
My hope was that we could use the list as a basic cutline of things that should get pulled over into their own discussions. For example, Declarative Shadow DOM is shipped / baseline, right? If so, then we don't have to pull that one over. Otherwise, sure I could create a single discussion for each item and we can use a thread per item to see if each item should be turned into its own discussion / issue. Let's chat on the next TPAC session if we have a minute. 👍 |
Session no. 3Notes: https://docs.google.com/document/d/1jOz2Mu8y49j81WPE7__sHkyoUQey6X09JNiYmEh4b1I/edit Action items
Held over
Chat history within...You |
Here's a link to an issue I just made re: our orgs and repos - #100 |
Session no .4Really great conversation about what we want to bring to the TPAC breakouts that have been proposed by Ryosuke. See the notes here. Action Items:
Held over:
|
Had some time to make a basic CSS Module Scripts demo, including sharing CSS between light and shadow DOM contexts and put together a draft comment to suggest a slight tweak to the goal of the TPAC CSS Modules Breakout session. Not sure if I need to evangelize as much as I am here or just get right to the point, but figured it wouldn't hurt. Let me know your thoughts and I can post there, or we can review first at our next planning session
|
More so for posterity / easy reference + access, just wanted to link out to the WICG TPAC 2024 planning session tracking issue - WICG/webcomponents#1065 And for each individual breakout session |
Unless anyone has any objections, I'll plan to cross-post my comment re: the CSS Modules Scripts breakout session description to the breakout issue later today. Just want to make sure if we are able to get a change in topic / focus, that it can gets captured before all the session scheduling starts happening. |
@thescientist13 I don't think we need to discuss CSS modules scripts at TPAC. Every implementor is on board, afaik, and Safari and Firefox just need to implement. I'm not sure what a goal would be for that part besides pinging them on implementation timeline. Declarative CSS modules scripts need to be discussed though. I thought the session was only on that. |
@justinfagnani FWIW, it was just raised in the WCCG Discord that Igalia has opened up a process for requesting features for Interop 2025, so would that be the better route for me to take then; as a Focus Area Proposal? edit: went ahead and opened an issue over on the Igalia repo for now - web-platform-tests/interop#703 |
@justinfagnani |
@thescientist13 oh, that's the exact same topic. I left a comment. |
Great TPAC, everyone, let's get ready for next year!! |
Starting the 18th or 19th of July, the Web Components Community Group will be hosting bi-weekly (one every two weeks) session for our preparation of 2024's "Web Components Spec/API status" report to the implementors gathered at TPAC. We'll keep this issue open while we continue meeting on a regular basis.
Join in the conversation!
The text was updated successfully, but these errors were encountered: