Upcoming HTML standard issue triage meeting on 3/4/2021

[past]

Last week a few community members, including the active HTML spec editors @annevk and @domenic, had a video call to triage some of the open issues. We spent an hour in a focused, high-bandwidth discussion and made some progress on a few spec issues. Here are the action items from that meeting:

1. @past to file an issue for the next meeting, inviting broader participation and announcing the agenda.
2. @annevk (or others) to create an [Agenda] tag for adding issues to the agenda.
3. On Define speculative HTML parsing #5959, @mfreed7 and @annevk to take a look after the meeting and comment on PR.
4. @mfreed7 and @annevk to analyze Add a final newline normalization for form payloads #6287, ideally with someone from WebKit as well. This comment summarizes the proposed spec vs. current browser behavior story.
5. @mfreed7 to review Obsolete <object usemap> #6283.
6. @mfreed7 and @annevk to look into this SVG issue.

This exercise seemed worthwhile so we will be repeating it on March 4th, 9 am PST for an hour. If you are 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 using the agenda+ label and we would like to invite anyone that can contribute to said issues to join us.

[annevk]

I created the agenda+ label and invited some more folks to the triage team so they can set it.

[domenic]

Perhaps people might like to discuss whatwg/meta#204 (not tagged since it's outside HTML), although there's plenty of time to have asynchronous discussion first.

[sideshowbarker]

I’d like to join the March 4 call

[annevk]

@sideshowbarker I added you.

[past]

Thanks everyone for attending! Here are the notes from the meeting (next one is at #6481):

Agenda

1. Welcome
2. New feature proposal: element
   1. Explainer in MSEdgeExplainers
   2. XUL popups as similar, prior art
   3. <dialog> open="" issue (Dialog should be better-behaved on misuse, probably #5802)
      1. Is it fine to fire an event synchronously after attribute mutation?
      2. Should it fire even when document’s browsing context is null? (Please no.)
3. Back-forward cache: Restoring focus
   1. Safari and Firefox diverge, which behavior should we pick and standardize? Consensus was to go with Safari’s behavior for interop.
4. Add Imperative Slot API
   1. General consensus apart from a corner case brought up by Ryosuke.
5. A process for requesting fast review on pull requests?
   1. Find a few PRs and pilot the idea there
   2. Self review before asking for review would help
   3. Using this process sparingly can help, using it always will defeat the purpose

Action Items

1. <popup>
   1. Anne, Domenic, Mason, Melanie to figure out <dialog> open="" issue
   2. Compare with XUL popups (Olli)
   3. Figure out taxonomy and ARIA interaction for : menus, teaching tooltips, etc. (Melanie, Domenic)
   4. Validate that custom elements can achieve popup="" behavior using JavaScript (Melanie)
2. BF cache
   1. Domenic to formally propose that we match Safari (don't blur on pagehide)
3. Imperative Slot API
   1. Olli and Mason to look at the issue and comment. Anne to ping Ryosuke
4. Fast review process
   1. Everyone to think of good PRs to pilot this idea.