-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Comments
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. |
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? |
Thank you all for attending today! Here are the notes from this meeting (the next one is at #8942): Agenda
Action Items
|
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.
The text was updated successfully, but these errors were encountered: