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

[past]

Today we held our monthly triage call (#7488) and I will post the meeting notes there in a bit. The next one is scheduled for March 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 agenda for tomorrow's meeting is rather sparse at the moment, so I encourage folks to tag more issues for discussion.

[Kaleidea]

@past I'm interested.

[annevk]

@Kaleidea could you please check your messages on Matrix? With that sorted I think it should be okay.

[Kaleidea]

I'm interested in the other ongoing topics. If Anne's referring to the search element: I've filed an appeal for formal review by the editor according to the workstream policy which the editor has not yet responded to. Until he responds, I have nothing to add.

[past]

@Kaleidea unfortunately I didn't see your message until now. Everyone should comment at least a day in advance of the meeting if they need me to see it, the meeting is very early in my work day.

Also, it isn't clear which editor you are expecting a response from, @annevk is certainly one of them.

[past]

Short meeting today, but thanks everyone for attending! Here are the meeting notes (next one is at #7677):

Agenda

1. Review past action items
   1. Domenic will merge the PR for adding a legacy encoding for Azeri.
      1. Done.
   2. Emilio will ping Mats on the <input type=password> should provide UI to show/hide its value thread.
      1. Waiting for Mats to reply. Emilio commented and will sanity check the proposal.
   3. Mason and Domenic will discuss Chromium's opinion on XML MIME types used for documents are not interoperable.
      1. Mason will take another look and Olli will comment on the thread with Gecko's behavior.
   4. Mason will investigate with the HTTP Archive and maybe implement Should 'true' count as truthy in parsing windowFeatures booleans. Let's also investigate "on" and non-1 integers.
      1. Progress was made, including adding tests. Will land the PR.
   5. Olli and Mason will leave feedback on the proposal for Valid/Invalid characters in document.createElement().
      1. Mason commented.
      2. Olli: annevk commented there and sounds like the issue needs some more thinking.
      3. Anne will summarize the current proposal and Domenic/Mason will ask for security review from Chromium folks.
   6. Joey will post an update on the Mouse events & disabled form controls thread.
      1. Joey commented.
   7. Domenic will investigate :active pseudo-class specification doesn't account for children/labels of disabled form elements.
      1. Closed after tests were added and a separate issue was filed for a secondary point.
   8. Domenic will discuss postMessage parts with Chromium folks for Add ability to query UserActivation state.
      1. Domenic is waiting for the spec parts from the team.
   9. Everyone's feedback is encouraged on URL-bar triggered prerendering.
      1. More discussions to follow asynchronously.
   10. Olli will ask Mozilla engineers for feedback on autocomplete attribute for street-address details. Feedback from WebKit is welcome.
       1. Olli asked, but no response yet.
   11. Emilio and Domenic will investigate further and leave feedback on blur and change events fire for elements removed from DOM.
       1. Carryover for the next time.
2. Carryovers from last time
   1. [Anne] Meta: Notice: Moving PR6478 to W3C Extension Specification
      1. Feedback was provided asynchronously, the issue is resolved now.
3. [Joey] Add hidden=until-found HTML attribute and beforematch event
   1. There was broad consensus on the approach.
4. [Brian] The PR for directionality in the shadow DOM has been approved by Elika and Tab, it's now waiting on Anne's review. Domenic asked to revert the template change. Brian will assist Eric with that.

Action Items

1. @mfreed7 will take another look at XML MIME types used for documents are not interoperable and @smaug---- will comment on the thread with Gecko's behavior.
2. @annevk will summarize the current proposal for Valid/Invalid characters in document.createElement() and @domenic/@mfreed7 will ask for security review from Chromium folks.
3. @emilio and @domenic will investigate further and leave feedback on blur and change events fire for elements removed from DOM.
4. @bkardell will assist @meyerweb with the PR for directionality in the shadow DOM and @annevk will review.

[Kaleidea]

Also, it isn't clear which editor you are expecting a response from, @annevk is certainly one of them.

@past No, not Anne, he did not work on the specification of the search element or answered any of the outstanding questions, nor do I expect him to. The appeal is addressed to Domenic, he leads that work, only he can answer the specific questions regarding his decisions.
Note that there are some procedural and ethical issues that I don't have the time to go into detail about, nor would it be productive to discuss in a meeting. As I've said I'm interested in being informed about a few other ongoing topics.
That applies to the next meeting too. Please sign me up early, so my request is not missed. Thank you.

[annevk]

@Kaleidea to be clear, I am a deputy editor of the HTML standard and discussing and reviewing text is certainly considered work around here. I've also answered several questions you had about that effort on Matrix as well as given it plenty of time during a call. There's nothing left to discuss here as far as I'm concerned and although I haven't checked again with Domenic, I'm pretty sure he agrees.