Upcoming HTML standard issue triage meeting on 4/7/2022

[past]

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

[Kaleidea]

Please sign me up, no specific topic to discuss this time.

[past]

Please sign me up, no specific topic to discuss this time.

Added you to the invite.

[andreubotella]

Please sign me up as well, for discussing #7575.

[past]

Please sign me up as well, for discussing #7575.

Added, thanks.

[past]

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

Agenda

1. Review past action items
   1. Mason will take another look at XML MIME types used for documents are not interoperable and Olli will comment on the thread with Gecko's behavior.
      1. Domenic and Olli commented. Mason will finish the Chromium testing and we'll ask for WebKit feedback.
   2. Anne will summarize the current proposal for Valid/Invalid characters in document.createElement() and Domenic/Mason will ask for security review from Chromium folks.
      1. Both done. Domenic to take a look next and Mason/Anne will ask for Chromium/Firefox security opinions.
   3. Emilio and Domenic will investigate further and leave feedback on blur and change events fire for elements removed from DOM.
      1. Domenic to comment and Emilio to test cross-browser behavior.
   4. Brian will assist Eric with the PR for directionality in the shadow DOM and Anne will review.
      1. Work is ongoing. Anne is waiting for input from Elika & Tab.
2. Carryovers from last time
   1. None.
3. [Mason] New feature proposal: Popup API
   1. Feedback is welcome. Anne: questions about popup attribute behavior on special elements. Brian: is this useful as a first step towards mixins that developers have asked for? More discussion should happen in the OpenUI meeting to include the rest of the community. Brian to add Emilio to that meeting. Olli to get feedback from Mozilla a11y people on their XUL <popup> experiences. Mason to summarize the open OpenUI issues in the HTML issue. After the open issues in the OpenUI repo are dealt with, an HTML PR would be the next step.
4. [Mason] Escaping multipart/form-data
   1. General positive sentiment in fixing this issue. A use counter would be useful to have an upper bound on potential breakage (on the server).
5. [Mason] <object> without "data" attribute probably needs to consider params to figure out its URL
   1. Mason will try to deprecate in Chromium, no objection from Mozilla.
6. [Forgotten?] Mouse events & disabled form controls
   1. This was likely tagged for a previous meeting, since no new comments had surfaced.
7. [Domenic] <object> element can tell whether child document loaded or not
   1. Didn't have time for this.
8. [Domenic] Exposing back/forward cache blocking reasons to sites
   1. Didn't have time for this.
9. [Domenic] Recommend iframe/img over embed/object for some content types
   1. Didn't have time for this.

Action Items

1. @mfreed7 will finish the Chromium testing for XML MIME types used for documents are not interoperable and we'll ask for WebKit feedback.
2. @domenic to take a look next at Valid/Invalid characters in document.createElement() and @mfreed7 / @annevk will ask for Chromium/Firefox security opinions.
3. @domenic to comment and @emilio to test cross-browser behavior on blur and change events fire for elements removed from DOM.
4. @annevk is waiting for input from Elika & Tab on the PR for directionality in the shadow DOM.
5. New feature proposal: Popup API: @bkardell to add @emilio to the OpenUI meeting. @smaug---- to get feedback from Mozilla a11y people on their XUL <popup> experiences. @mfreed7 to summarize the open OpenUI issues in the HTML issue.
6. <object> without "data" attribute probably needs to consider params to figure out its URL: @mfreed7 will try to deprecate in Chromium.