Upcoming HTML standard issue triage meeting on 11/10/2022

[past]

Today we held our biweekly triage call (#8385) and I will post the meeting notes there in a bit. The next one is scheduled for November 10, 4 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 and we would like to invite anyone that can contribute to said issues to join us.

[past]

Hey @whatwg/html-triage, there is still room in the agenda for more topics.

[past]

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

Agenda

1. Review past action items
   1. Olli and Emilio to find a Firefox rep, Anne to find a Safari rep for a longer discussion of autocomplete attribute for street-address details.
      1. Mason wants to ping the request for implementer points of contact to participate in a half-day autocomplete attribute workshop.
      2. Smaug: pinged serg (since Tim is doing non-autocomplete stuff)
      3. It would be good to get somebody from WebKit too.
   2. Anne will find the WebKit experts and confirm that they are OK with the timing proposal to make the focus fixup rule more explicit. Mason or Joey to add feedback on what Blink is using for removal.
      1. More discussion followed and more proposals were made.
      2. No objections to Domenic's proposal: no events on removal, but we will reopen the discussion about a new dedicated (non-focus) event for node removal to solve the use case. Maybe Chromium won't make the change to stop firing events on removal until that is ready, but that will at least allow us to move forward on rigorously speccing and testing the focus fixup rule and getting interop there.
2. Carryovers from last time
   1. [Anne] Align with DOM DocumentFragment adoption changes
      1. The compat issue seems scary, we'll discuss it more thoroughly when Anne is attending.
   2. [Joey] New feature proposal: Popup API
      1. The latest update addressed review feedback. Olli will review and discuss with Emilio the latest PR. Emilio's security issue is now moot. The current version only uses one event. Olli will look into how well XUL popup events align with the proposal. The explainer is almost up to date but has some stalled PRs; the spec should be more complete and detailed.
3. New topics
   1. [Domenic] Define :blank pseudo-class behavior
      1. Proposal by web developer: Define :blank pseudo-class behavior #8451 (comment) (expand the <details>)
   2. [Domenic] Define :user-valid and :user-invalid pseudo-classes
      1. [smaug]: :user-invalid & :user-valid browser support web-platform-tests/interop#178 (comment) can be a useful comment
      2. Mason will review these proposals. Olli will review the :blank proposal. Domenic to reach out to Tab / Elika (as Selectors editors) to get them to weigh in on the proposals too.
   3. [Mason] Let me know what you think about the Declarative Shadow DOM PR
      1. Domenic and Mason will sync offline.

Action Items

1. @annevk to find a Safari rep for a longer discussion of autocomplete attribute for street-address details.
2. @smaug---- will review and discuss with @emilio the latest PR for New feature proposal: Popup API. @smaug---- will look into how well XUL popup events align with the proposal.
3. @mfreed7 will review the pseudo-classes proposals. @smaug---- will review the :blank proposal. @domenic to reach out to Tab / Elika (as Selectors editors) to get them to weigh in on the proposals too.
4. @domenic and @mfreed7 will sync offline on the Declarative Shadow DOM PR.