Closed Westbrook closed 2 weeks ago
If it'll help, I'd like to give a short (5min) overview of the additional DOM Parts ideas and what's motivating them. I can make a few slides for it.
@Westbrook I think I'm the owner of the two gcal events now, and the associated Meet meetings, so I think we're all set there. I'll make sure another Googler or two is an owner/cohost so they can adjust settings and admit people if neccessary.
Other logistics questions:
- Recordings: I think we've usually not recorded these meetings due to preferences from individuals and employers. Just confirming that I don't think we'll even need to raise the question at the meeting.
Yeah, please don't record the video/audio.
@rniwa can you add this as an issue under "Declarative adoptedStylesheets": https://github.com/WICG/webcomponents/issues/939?
I would like to attend (virtually), i am interested in Custom Elements, Shadow DOM and Scoped Custom Element Registries.
I'd also like to attend virtually. I don't know why I never got any communication on this. It doesn't seem like anyone from FAST or perhaps even from Microsoft was made aware of this event. Both myself (architecture and technical advisor on FAST) and @Chrisdholt (representing Microsoft) would like to attend. I have opened up my schedule to participate on both days. @Westbrook or @justinfagnani Can you assist please?
Update: Westbrook reached out and got me the info. Looks like there were a combination of things that happened leading to the missing information. All is sorted. Thanks!
Hey everyone... I think there was a little snafu with the calendar events and when @Westbrook transferred ownership of them to me they by default went to my personal calendar. So I think they might not have been listed at the links Westbrook posted above for a while. Apologies!
I transferred them back to the WCCG calendar, though there are now two events (I presume Westbrook created some new ones while I was sleeping in Pacific time). They have the same Meet link, so that's not a problem. If I invited you specifically to an event, you're still there.
To surface them again, some links:
See you there!
edit: and I had to make the effects public too, which is now done.
We're having a separate F2F meeting to discuss DOM parts in more depth. Please refer to https://github.com/WICG/webcomponents/issues/999 for scheduling & agenda of that meeting.
@annevk how do you want to run "Web Components pain points in general" tomorrow?
25 min isn't much time, I'd imagine we only have enough time to list some things?
WC pain points to discuss:
pure
function in ES as tool for multithreading legitimate even in main JS threadWe'll have a separate F2F to discuss cross-root ARIA. For scheduling and agenda, please see #1005.
Here is the link to the notes doc: https://docs.google.com/document/d/1XWp4ndl5bthoxhnqR9Ly1SYvYcmXw1eTrappoMXsuH4/edit?usp=sharing
I've locked down edit-ability on the public link. If you want to change something in there, let me know and I can add you as an editor.
I added an issue to schedule the "Styling and Theming" breakout: https://github.com/WICG/webcomponents/issues/1006
Shoot. I wrote here something about lazy loading component, moved it there. Oops!
It's been quite a while now, but it seems like it would be a good idea for us to gather and discuss some of the really exciting proposals and specs that have been coming up or coming together in support of new functionality in the world of web components.
In concert with the WCCG, I'd like to propose we work toward making something happen the first half of April 2023. For out part, having the discussion is the most important part of the event, but we'd be interested in your thoughts on live vs virtual vs hybrid sessions as well.
Happy to take suggestions on Agenda content below:
I've created this poll to gather the availability of interested parties through the month of April: https://www.when2meet.com/?18702051-ib5Wi
As we'll be virtual there is room for spreading the conversation out over more than one day, but please try to mark availabilities of at least 90 minutes each so we can find sizable chunks of time to get as deep into the various APIs we'd like to target as possible.