Upcoming HTML standard issue triage meeting on 8/5/2021

[past]

On July 1st we held our monthly triage call (#6739) and I will post the meeting notes there in a bit. The next one is scheduled for August 5th, 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.

[bkardell]

Please include me

[past]

Please include me

Done!

[stubbornella]

Please include me.

[bkardell]

fwiw i have passed along the info to @meyerweb - if you could include him too so it winds up on his calendar tho that would be great. Eric has recently submitted a large batch of tests encompassing all of the pens/cases flying around for discussion on #3699 - it already has the agenda+ issue label so we'd love to try to see if these tests cover cases and if/where there is disagreement.

[past]

Added both Nicole and Eric.

[past]

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

Agenda

1. Review past action items
   1. [Domenic & Anne] For canceling file upload, structured clone, and reportError(), get the PRs ready to land: browser bugs, tests, etc.
      1. All done!!
   2. [Domenic] write up input/composed summary and spec PR.
      1. Filed an issue, spec PR still remains as a TODO
   3. [Domenic] review spec
      1. Review done, further progress soon
   4. [Scott] blackbox testing of timer behavior on various platforms
      1. Scott did some testing, it will be risky for compatibility
   5. [Mason] file browser bugs for text/media/plugin no-quirks.
      1. Mozilla, WebKit bugs filed.
2. [Domenic] Removing plugins?
   1. Domenic will take point on moving forward in the remaining bits, there is appetite to continue here.
3. [Melanie] FYI on this issue in Open UI: [select] To what extent should customizable select implement the old <select>'s interface? · Issue #380 · openui/open-ui (github.com)
   1. Everyone is encouraged to provide input
4. [Emilio/Joey] Expand <details> for find-in-page and element fragments
   1. Agreement that we need WPT tests. Joey will file an issue for WPT support for find in page (which sometimes behaves differently from window.find).
5. [Anne] Standardize a popup's condition and UI opened by window.open
   1. Waiting for Apple to provide feedback and Mozilla to move forward with implementation
6. [Domenic] Proposal: Add a way to open programmatically a date picker
   1. Domenic will kick off a survey of all pickers and how they can be opened, how click() behaves, etc. Emilio suggests that maybe focusing the element should be required
7. [Eric] It is unclear how directionality should be inherited into Shadow DOM
   1. Tests are ready to be added to WPT. Normative definition is needed (Eric). Will get feedback from CSS WG folks (Brian). Eric will respond to Olli's question in the GH issue
8. [Mason] Should input/change events be fired when the UA restores a form?
   1. Mason will document what Chrome does in back/forward cases vs. document/tab close/restore cases. Melanie will bring this up with OpenUI folks.
9. [Domenic] Add &nnbsp; entity for U+202F
   1. Didn't have time for this topic.
10. [Domenic] setCustomValidity() seems pointless on
    1. Didn't have time for this topic.
11. [Domenic] Consider creating an HTML search element
    1. Didn't have time for this topic.

Action Items

1. Domenic will take point on moving forward in the remaining bits for removing plugins, there is appetite to continue here.
2. Everyone is encouraged to provide input on this issue in Open UI.
3. Agreement that we need WPT tests. Joey will file an issue for WPT support for find in page (which sometimes behaves differently from window.find). Done!
4. Domenic will kick off a survey of all pickers and how they can be opened, how click() behaves, etc.
5. Eric will provide a normative definition for directionality inheritance. Brian will seek feedback from CSS WG folks. Eric will respond to Olli's question in the GH issue.
6. Mason will document what Chrome does in back/forward cases vs. document/tab close/restore cases. Melanie will bring this topic up with OpenUI folks.