December Meeting Agenda

[Westbrook]

For those of you who would like to take part in the December meeting of the Web Components Community Group, please share your availability here as we work to schedule the right day/time to gather. Don't forget, all WCCG events are listed on this calendar.

If you've topics that you'd like to have included in the December meeting, please comment below. Any additional information and/or pre-reading that you could share with fellow attendees would be much appreciated.

Ongoing meeting topics are as follows:

• preparation for the Q1 Face-to-Face with implementors
  • these are the topics from TPAC that we're looking to follow up on
  • ways that the CG can be more active in "landing" specs/APIs
• review of issues/PRs/etc submitted to the Community Protocols project
• longer future spec discussions for Face-to-face meetings with implementors later in 2024

While you're waiting, join the conversation on Discord!

[o-t-w]

I would like to add HTML modules to the agenda.

Back in 2019 there was excitement about the intent to implement by the Edge team. Because of all the spec changes with what were then called import assertions, this got stalled. The last remaining issue with the import attributes spec was closed recently. Import attributes are supported in Safari beta. Ken from TAG said: "As far as I was told, the current focus is on first doing JSON modules, then CSS modules and then revisit HTML modules". The standardisation of CSS modules and JSON modules is now complete.

It feels like HTML modules have been forgotten about in everyone's agenda. I wonder if there is more that can be done to try to recreate some momentum for this?

[matthewp]

I would like to add two things:

• Clarification on the current barrier to a merged proposal. I am explicitly not wanting to debate what the barrier should be, but to clarify what it currently is. The outcome of this discussion would be an update to the readme.
• This proposal template: Add a proposal template webcomponents-cg/community-protocols#47

[nolanlawson]

Just to clarify: it's at December 7th, 11am ET/8am PT/5pm CET

I would actually like to discuss defer-hydration (webcomponents-cg/community-protocols#15). My goal is to understand 1) what an interoperable implementation would look like, and 2) if any other WC frameworks are considering implementing it or have implemented it (other than Lit).

[Westbrook]

@o-t-w in preparation for discussing this next month and at Face-to-Faces into the new year, would you be able to submit a PR to https://github.com/WICG/webcomponents/blob/gh-pages/proposals/html-modules-explainer.md that supported the more current Import Attributes syntax? I know normalizing that to the latest APIs will be a useful part of the conversations there.

[o-t-w]

@Westbrook PR here I've updated the syntax and updated one of the issue links.

[anlexN]

today, web component have 4 lifecycle by itself:

• connectedCallback()
• disconnectedCallback()
• adoptedCallback()
• attributeChangedCallback()

but stenciljs and lit add more lifecycle.

from the view of standard, are they resonable? or will standard add more lifecycle in the future too?