Upcoming HTML standard issue triage meeting on 2/3/2022

[past]

Today we held our monthly triage call (#7385) and I will post the meeting notes there in a bit. The next one is scheduled for February 3, 9 am PST. 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]

The same scheduling conflict that we've had for the last couple of times is occurring again, but I am told it's (for real!) for the last time. I plan to move this meeting an hour later again to accommodate the several folks who need to be in both meetings, unless a large number of people tell me otherwise.

[Kaleidea]

I'm also interested. No questions this time.

[past]

I'm also interested. No questions this time.

Added, thanks.

[past]

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

Agenda

1. Review past action items
   1. Olli & Anne will send Domenic more info on popstate/hashchange dispatching doesn't match what browsers do.
      1. Domenic commented.
      2. Olli commented.
   2. Henri will think a bit more about the parser implications with adding the <search> element.
      1. Will revisit in the future, when Henri has thought about this
   3. Mason will review and comment on the Use the real tokenizer and tree builder for meta scan thread.
      1. Mason commented. Will continue discussing asynchronously.
   4. Mason to solicit feedback for adding a legacy encoding for Azeri.
      1. Mason commented. Domenic will merge the PR.
2. Carryovers from last time
   1. Tess commented to the <input type=password> should provide UI to show/hide its value thread.
      1. Emilio will ping Mats and we'll discuss again in the future.
   2. [Anne] XML MIME types used for documents are not interoperable
      1. Mason and Domenic to discuss Chromium's opinion.
   3. [Mason] Should 'true' count as truthy in parsing windowFeatures booleans?
      1. No objections, Mason will investigate HTTP archive and maybe implement. Let's also investigate "on" and non-1 integers.
   4. [Domenic] Valid/Invalid characters in document.createElement()
      1. Olli and Mason to leave feedback on the proposal.
   5. [saschanaz] Mouse events & disabled form controls
      1. Will discuss it next time. Joey will post an update on the thread.
   6. [Anne] Meta: Notice: Moving PR6478 to W3C Extension Specification
      1. Will discuss it next time.
   7. [Domenic] :active pseudo-class specification doesn't account for children/labels of disabled form elements
      1. Need to test Safari's behavior. Domenic will investigate.
   8. [Domenic] Add ability to query UserActivation state (PR)
      1. navigator.userActivation: let's do it.
      2. Domenic will discuss postMessage parts with Chromium folks.
3. [Domenic] URL-bar triggered prerendering
   1. Everyone's feedback is encouraged. Olli is positive.
4. [Dominic] autocomplete attribute for street-address details
   1. Olli will ask Mozilla engineers for feedback. Feedback from WebKit is welcome.
5. [Domenic] blur and change events fire for elements removed from DOM
   1. Emilio and Domenic will investigate further and leave feedback.

Action Items

1. @domenic will merge the PR for adding a legacy encoding for Azeri.
2. @emilio will ping @MatsPalmgren on the <input type=password> should provide UI to show/hide its value thread.
3. @mfreed7 and @domenic will discuss Chromium's opinion on XML MIME types used for documents are not interoperable.
4. @mfreed7 will investigate with the HTTP Archive and maybe implement Should 'true' count as truthy in parsing windowFeatures booleans. Will also investigate "on" and non-1 integers.
5. @smaug---- and @mfreed7 will leave feedback on the proposal for Valid/Invalid characters in document.createElement().
6. @josepharhar will post an update on the Mouse events & disabled form controls thread.
7. @domenic will investigate :active pseudo-class specification doesn't account for children/labels of disabled form elements.
8. @domenic will discuss postMessage parts with Chromium folks for Add ability to query UserActivation state.
9. Everyone's feedback is encouraged on URL-bar triggered prerendering.
10. @smaug---- will ask Mozilla engineers for feedback on autocomplete attribute for street-address details. Feedback from WebKit is welcome.
11. @emilio and @domenic will investigate further and leave feedback on blur and change events fire for elements removed from DOM.