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

Upcoming HTML standard issue triage meeting on 2/23/2023 #8873

Closed
past opened this issue Feb 9, 2023 · 3 comments
Closed

Upcoming HTML standard issue triage meeting on 2/23/2023 #8873

past opened this issue Feb 9, 2023 · 3 comments
Labels
agenda+ To be discussed at a triage meeting

Comments

@past
Copy link

past commented Feb 9, 2023

Today we held our biweekly triage call (#8786) and I will post the meeting notes there in a bit. The next one is scheduled for February 23, 3 pm PST. Note that this is 2 weeks later in an APAC+America friendly time.

People interested in attending the next call please respond here or reach out privately to me or the spec editors. We will be tagging issues for the next call again using the agenda+ label in all WHATWG repos and we would like to invite anyone that can contribute to said issues to join us.

@past past added the agenda+ To be discussed at a triage meeting label Feb 9, 2023
@annevk
Copy link
Member

annevk commented Feb 9, 2023

As I cannot attend at that time slot, with regards to ShadowRealm: I think the main thing I'm interested in is getting that PR unstuck and that probably requires @domenic to chime in.

I suspect we won't have quorum to discuss the HTML parser API ideas, but in case we do my thinking is in the relevant issue.

@domenic
Copy link
Member

domenic commented Feb 15, 2023

With regard to ShadowRealm: honestly, it is a very large PR and it is hard for me to prioritize, as I don't work on that area of the web platform currently. I can still do my best to review as part of my general HTML editor duties, but there is no need to block on me, and if another editor is more invested in getting that landed, they should feel free to take over.

It does seem that there have been recent decisions made which haven't made their way into the PR (and/or into Web IDL), namely the idea of adding a new ShadowRealmGlobalScope object and using that: #7591 (comment) . So maybe that's the next step?

@past
Copy link
Author

past commented Feb 23, 2023

Thank you all for attending today! Here are the notes from this meeting (the next one is at #8942):

Agenda

  1. Review past action items
    1. Chris will summarize the discussion around Add convenient, ergonomic, performant API for sorting siblings and the agreed upon next steps.
      1. Joey summarized, Tab and others commented on the proposal. Marcos & Anne to kindly look for ways the proposed solution here might run into problems.
  2. Carryovers from last time
    1. [Domenic] <input type="time"> : Time vs. duration
      1. We need some answers to the questions Anne posted in the issue.
    2. [Anne] JavaScript ShadowRealm proposal integration
      1. Anne and Domenic commented. Next step would be for the PR to include the new ShadowRealmGlobalScope object.
    3. [Mason] Add DOMParser option to parse declarative shadow DOM
      1. Will discuss it next time.
  3. New topics
    1. [Anne] GC for cached attr-associated elements?
      1. Consensus in the room is that this is fine, more feedback is welcome.
    2. [Anne] Shadow DOM and ElementInternals ARIAMixin properties
      1. Feedback is welcome on Anne's PR, will discuss this again next time.

Action Items

  1. @marcoscaceres & @annevk to kindly look for ways the proposed solution here might run into problems.
  2. Feedback from everyone is welcome on @annevk's PR to Give ElementInternals element-reflecting attributes more power, will discuss this again next time.

@past past closed this as completed Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agenda+ To be discussed at a triage meeting
Development

No branches or pull requests

3 participants