06:32:08 RRSAgent has joined #webcomponents 06:32:12 logging to https://www.w3.org/2023/09/13-webcomponents-irc 06:32:12 RRSAgent, do not leave 06:32:12 RRSAgent, make logs public 06:32:14 Meeting: Web Components API/Specs Report and Alignment 06:32:16 Chair: Westbrook, Keith Cirkel 06:32:20 Agenda: https://github.com/w3c/tpac2023-breakouts/issues/17 06:32:22 clear agenda 06:32:25 agenda+ Pick a scribe 06:32:26 agenda+ Reminders: code of conduct, health policies, recorded session policy 06:32:28 agenda+ Goal of this session 06:32:30 agenda+ Discussion 06:32:32 agenda+ Next steps / where discussion continues 07:20:14 tidoust has joined #webcomponents 07:32:15 westbrook has joined #webcomponents 07:32:53 Howdy IRC! Is Keith in the room that coudl help make sure Zoom in connected? 07:34:06 Jesse_Jurman has joined #webcomponents 07:34:47 Justin_F_ has joined #webcomponents 07:35:03 rictic has joined #webcomponents 07:35:37 Justin_F__ has joined #webcomponents 07:36:09 JustinFagnani has joined #webcomponents 07:36:13 bennyp has joined #webcomponents 07:36:20 eisenbergeffect has joined #webcomponents 07:36:33 JohnRiv has joined #webcomponents 07:36:59 JaredW has joined #webcomponents 07:40:31 JaredW_ has joined #webcomponents 07:52:14 Joey: Scoped Custom Element Registries still have a couple of open issues 07:53:09 Ryosuke: main hold back are minor details on what happens with same name in two registries and then move between trees. 07:57:56 Slot content question: would this strip whitespace by default? 07:59:04

<- has whitespace (therefore has slotted content?) <- no content at all 07:59:25 this gotcha can affect authors who use html formatting tools 07:59:54 https://github.com/w3c/csswg-drafts/issues/7922 08:00:06 christianliebel has joined #webcomponents 08:01:01 wicg/webcomponents issue for detecting filled slots: https://github.com/WICG/webcomponents/issues/936 08:02:30 Ryosuke: raise /thing/ combinator at the CSS WG as a real thing or not. 08:03:35 ryosuke: maybe we need this as a pseudo class 08:04:14 justin: walks through the JS path the allows for content detection, requiring double render and blocks SSR 08:06:13 ryosuke: https://github.com/w3c/csswg-drafts/issues/6867 seems slightly more attainable than https://github.com/w3c/csswg-drafts/issues/7922 at least in terms of work 08:06:49 justin: separating has from desendents is likely a smaller conversation 08:06:54 ryosuke: agrees 08:08:37 ryosuke: is CSSWG is at TPAC then we should try and get this into the convo there 08:11:59 Declarative Custom Elements ? 08:12:46 Justin: what DCE means could be unclear 08:13:01 Justin: CG could support community out reach to clarify what that means. 08:13:10 Justin: thinks there is interest 08:13:46 Justin: doesn't get to the reports because of "broken things", but collaborative interest is great to hear 08:13:56 ryosuke: gathering use cases is a good next step 08:14:24 ryosuke: XBL was some version of this, as CSS essentially declared a shadow root onto something 08:15:16 ryosuke: Mozilla should have some feedback on the experience of shipping (and unshipping ) XBL 08:16:29 ryosuke: buggest win may be the platform performance wins that a browser could bring 08:16:33 *biggest 08:16:50 Justin: long road to DCE starts with DOM parts 08:17:52 Ryosuke: DCE includes some level of replacing something in your tree 08:18:07 Ryosuke: DCE could take progress even without templating 08:18:30 https://github.com/WICG/webcomponents/issues/1009 08:18:47 Justin: "non-linear" progress in this area could confuse consumers, but could be marketed correctly 08:19:09 Justin: looking for clarity on whether DCEv1 actually needs templating. 08:21:22 Ryosuke: happy to meet virtual, but feels that a process (like what's in CSSWG) is what's missing. 08:23:33 Ryosuke: discussion happens but conclusions are not made due to _something_... 08:24:15 Joey: OpenUI does this by having "resolutions" and blog posts after weekly meetings 08:25:14 Justin: is there a WG that we work under? or can we just make proposals to the DOM specs? 08:27:29 Would be good to see these things as a consumer of the CSSWG. 08:27:46 Maybe part of this is having a clearer process of (a) is there a proposal(s) for [X] spec, and (b) what is the current status? Can the CG surface those more regularly? 08:27:52 James: the level is less important than the tight agreement of an implementor 08:29:36 Justin: do we need a WG or a process? 08:30:04 To group: Any one against a quarterly face to face? 08:31:48 Ryosuke: everyone agrees we can! 08:32:01 Ryosuke: do we want more structure? 08:32:08 Ryosuke: _probably_ 08:32:25 Ryosuke: include resolutions in those meetings. 08:35:07 JohnRiv has joined #webcomponents 08:39:19 JohnRiv has joined #webcomponents 08:43:14 JohnRiv_ has joined #webcomponents 09:01:00 tidoust has joined #webcomponents 09:06:09 edgar has joined #webcomponents 09:06:09 xiaochengh has joined #webcomponents 09:06:09 JohnRiv has joined #webcomponents 09:06:09 jarhar has joined #webcomponents 09:06:09 oriol has joined #webcomponents 09:06:09 annevk has joined #webcomponents 09:06:09 astearns has joined #webcomponents 09:06:16 JohnRiv has joined #webcomponents 09:06:16 Google Doc for minutes: https://docs.google.com/document/d/1e1anpmGiYyAHZYg7oRkLVsGrqYWTjFCKSqyjp8p9n4I/edit 09:07:38 current scoped custom element registry explainer: https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md 09:09:49 JohnRiv has left #webcomponents 09:47:31 The room microphone situation is bad. It's very difficult to hear 10:10:03 flackr has joined #webcomponents 10:17:31 ChrisLorenzo has joined #webcomponents 10:18:22 hsivonen has joined #webcomponents 10:19:56 jocelyntran has joined #webcomponents 10:22:01 Google Doc for minutes for DOM Parts - https://docs.google.com/document/d/1ZmKfLXGvgmoF0p_gZMngCic3pLv7IJyD3TIgBZVKP0g/edit 10:24:50 for the minutes, who asked the question? 10:27:06 JaredW has joined #webcomponents 10:28:33 flackr has joined #webcomponents 10:35:26 q? 10:48:19 Previous issue on part syntax: https://github.com/WICG/webcomponents/issues/688 12:05:13 tidoust has joined #webcomponents