Skip to content
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

2024 TPAC planning #1065

Closed
rniwa opened this issue Aug 12, 2024 · 13 comments
Closed

2024 TPAC planning #1065

rniwa opened this issue Aug 12, 2024 · 13 comments

Comments

@rniwa
Copy link
Collaborator

rniwa commented Aug 12, 2024

Are there any topics we should discuss during TPAC in breakout sessions?

@justinfagnani
Copy link
Contributor

justinfagnani commented Aug 12, 2024

A few things I'd like to discuss:

  • Finishing scoped element registries MVP. I think the previous round of open questions was resolved, but there's a newer topic of how to use scopes when constructing detached trees that would be good to cover. I can help prep things to show the current status for this one.

  • Theming. It's been a while since we tried to talk about theming from a high level. A lot of people are interested in "open styleable" for theming uses cases, not necessarily the backwards-compatibility with existing stylesheets use case, so I think it'd be good if we took some of the pressure off open-styleable to be all things by opening up the theming discussion again.

  • Declarative CSS modules (deduping per-component CSS in SSR). Microsoft is very interested in this now and dedicating some time to work on it.

  • DOM Parts, especially goals and constraints. Chrome's experimentation is ongoing, but so far a native implementation doesn't look like a slam-dunk performance win. Are there DX goals that justify the feature, or higher level features (like templating) that we should pursue?

I don't know if they all warrant their own session or should be grouped.

@rniwa
Copy link
Collaborator Author

rniwa commented Aug 13, 2024

@Westbrook : anything to add?

@Westbrook
Copy link
Collaborator

The couple of things I can think of based on our recent meetings:

Baring any bad news, they should all fit as smaller conversations in a larger window, rather than needing their own individual blocks.

@rniwa
Copy link
Collaborator Author

rniwa commented Aug 14, 2024

Proposed scoped custom element registry as session: w3c/tpac2024-breakouts#26

@rniwa
Copy link
Collaborator Author

rniwa commented Aug 14, 2024

Proposed open styleable shadow tree & theming as a session: w3c/tpac2024-breakouts#27

@rniwa
Copy link
Collaborator Author

rniwa commented Aug 14, 2024

Proposed DOM parts as a session: w3c/tpac2024-breakouts#28

@rniwa
Copy link
Collaborator Author

rniwa commented Aug 14, 2024

Proposed CSS modules as a session: w3c/tpac2024-breakouts#29

@rniwa
Copy link
Collaborator Author

rniwa commented Aug 14, 2024

Proposed Web Components & ARIA as a session: w3c/tpac2024-breakouts#30

@justinfagnani
Copy link
Contributor

Re: DOM Parts. I wrote down one of the things I was thinking of as a motivation for DOM Parts outside of the pure performance vs a library of the low-level API, declarative templates in JS: #1069

@LeaVerou
Copy link

Proposed this breakout for a different theming issue (sharing design tokens between WCs and host page): w3c/tpac2024-breakouts#92 / https://www.w3.org/events/meetings/a9540089-cb3a-413b-966a-8c1034b31b11/
Would love to have a co-chair if anyone is interested! Sadly, they scheduled it at the same time as two of other WC breakouts (despite them being listed as conflicts) 😖

@keithamus
Copy link
Collaborator

keithamus commented Sep 20, 2024

Happy to co-chair wherever I have no other conflicts.

@justinfagnani
Copy link
Contributor

Speaking of chairs and co-chairs... @rniwa since you proposed these breakouts, you might be on the hook for them, but would you like other to take over chairing for them? I can certainly do a few of the ones I suggested.

@Westbrook
Copy link
Collaborator

@rniwa many thanks again for bringing all these sessions together. After another great TPAC, closing this scheduling issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants