Upcoming HTML standard issue triage meeting on 12/8/2022

[past]

Yesterday we held our biweekly triage call (#8446) and I will post the meeting notes there in a bit. The next one is scheduled for December 8, 9 am PST. Note that this is 4 weeks later in an America+Europe friendly time.

I propose that we skip the meeting scheduled for November 24 as it falls on a public holiday in the US, which will severely limit the usual attendance. If people disagree and want to meet instead, then let me know in the comments.

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.

[domenic]

Let me flag #8525, which I just closed and so might not show up when assembling the agenda, for potential low-priority discussion. I won't be there, unfortunately, but maybe the people who are will have some thoughts.

The main discussion question is: "Is there any implementer interest in making <meta name="referrer"> behave reasonably? Or should we stick with the now-specced semantics that all browsers follow, but are kind of bad?"

[past]

Apologies Domenic, but I was out and missed that comment (and the meeting). Happy to add it to the next one if you'd like.

[past]

Thanks everyone for attending and especially @cwilso for hosting in my absense! Here are the notes from this meeting (the next one is at #8614):

Agenda

1. Review past action items
   1. Anne to find a Safari rep for a longer discussion of autocomplete attribute for street-address details.
      1. Did this happen?
      2. Anne will reply (by) tomorrow.
   2. Olli will review and discuss with Emilio the latest PR for New feature proposal: Popover API. Olli will look into how well XUL popup events align with the proposal.
      1. In XUL
         1. Popupshown (fired after the popup is already visible) is used for example to implement autohide after some time. And possibly more important use case is to focus certain element in the popup.
         2. Popuphiding isn't used too often and popuphidden could have been used in many places.
         3. Popuppositioned fires if the position or size changes
         4. Position attribute is used every now and then to control where the popup is shown relative to the anchor element
      2. Didn't discuss with Emilio yet.
      3. Mason would like feedback to be added here: [popup] Consider to add popupshowing, popupshown, popuphiding and popuphidden events openui/open-ui#342
   3. Mason will review the pseudo-classes 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.
      1. Done.
      2. Need more details for :user-valid and :user-invalid.
   4. Domenic and Mason will sync offline on the Declarative Shadow DOM PR.
      1. There have been quite a few comments in the PR.
2. Carryovers from last time
   1. None.
3. New topics
   1. [Emilio] Should padding be respected on "natively styled" form controls?
      1. Mason to dig in and comment
   2. [Domenic] What should happen when the last valid <meta name="referrer" content="..."> tag is removed?
      1. resolved
   3. [Tim] <form method="dialog"> should probably not check for noopener
      1. Mason to take a look
   4. [Anne] Align with DOM DocumentFragment adoption changes
      1. Postponed
   5. [Panos] Move APAC/America-friendly triage meeting time to 08:00 Tokyo time / midnight Berlin / 15:00 San Francisco
      1. Last call for objections before making the change.
   6. [Gary] Preserve the cursor shape during drag-n-drop
      1. Needs response to smaug's comment before a PR should be authored.

Action Items

1. @emilio to investigate :user-valid and :user-invalid
2. (Tentative action as they were not present.) @tabatkins / @fantasai to comment on the :blank issue