Upcoming HTML standard issue triage meeting on 11/4/2021

[past]

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

[domenic]

I've added #6763 on behalf of @fserb and @mysteryDate (/cc @yoavweiss @miketaylr) to discuss throwing vs. non-throwing behavior. Ideally we'd do that earlier in the call so that the folks who are attending specifically for that issue don't have to stick around for the whole call :)

[past]

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

11/4/2021

Agenda

1. [Domenic] CanvasFilter objects as input to CanvasRenderingContext2D.filter attribute
   1. [Discussing first so that the folks who are attending specifically for this issue don't have to stick around for the whole call.] The editors accept the non-throwing behavior.
2. Review past action items
   1. Discuss next steps on the proposed search element.
      1. Some discussion has happened. Next steps: Domenic and others to spec this. Anne brought up display:block.
   2. Land tests on the Improve autofocus and delegatesFocus interaction PR.
      1. Done.
   3. Mason will bring more feedback on the issue about ensuring PDF browsing contexts have no DOM.
      1. Mason to provide the feedback from the Chromium issue so far. Will revisit when more info is available.
   4. Mason will wait for use counter for <object> without "data" attribute probably needs to consider params to figure out its URL to reach stable and then investigate HTTPArchive.
      1. Some investigation happened, need to do more. Mason will add some example URLs in the issue, Domenic and Anne to take a look at them.
   5. Revisit :active pseudo-class specification doesn't account for children/labels of disabled form elements after everyone had more time to think about it.
      1. No new comments on the issue. Mason and Emilio agree on the validity of the issue, Domenic will look into it and post a comment.
   6. Deliver feedback to the Renderblocking attribute issue.
      1. Xiaocheng will post an update to the issue.
   7. Anne will talk to arai and come back with another proposal around Standardizing a popup's condition and UI opened by window.open.
      1. Done.
   8. Mason will look into the issue Focus the dialog element instead of the first focusable item and discuss it with Domenic.
      1. More comments appeared in the issue. Progress has been made, will keep working on it.
3. Carryovers from last time
   1. Domenic will do extra testing for browser behavior with no user activation. Consensus that the proposal is reasonable. Also need to think about whether third-party frames can show pickers. (Modals are on top of other pages, file pickers are particularly scary.)
      1. Domenic gave a quick update.
   2. On Directionality in Shadow DOM, Eric will present a proposed text change to the CSS WG and get their feedback.
      1. Elika has commented on the issue with the CSS WG consensus. There is a need for an HTML spec PR.
   3. Mason rolled back the recent Chromium change around element restoration and Domenic will send a PR to clarify the spec about not firing events in these cases.
      1. Done.
   4. On custom validity checks for fieldsets, the group would like to see a little more developer support. There is also some small compat risk that is being considered. Domenic will try to get more signals.
      1. Domenic tweeted, some people seem interested but not really a lot. Happy to leave this as an open "needs implementer interest" request indefinitely and no longer monitor it on this call.
4. [Anne] <input type=password> should provide UI to show/hide its value
   1. Chrome has this behavior behind a flag due to interop issues. Folks will add feedback to the issue, there is general agreement on the usefulness of the feature along with some concerns about site compatibility.

Action Items

1. Domenic and others will spec the proposed search element.
2. Mason will add some example URLs in the <object> without "data" attribute issue, Domenic and Anne will take a look at them.
3. Domenic will look into the :active pseudo-class specification doesn't account for children/labels of disabled form elements and post a comment.
4. Xiaocheng will post an update to the Renderblocking attribute issue.
5. We need volunteers for an HTML spec PR on Directionality in Shadow DOM.
6. Everyone is encouraged to add feedback to the issue: <input type=password> should provide UI to show/hide its value.