Upcoming WHATNOT meeting on 4/25/2024

[past]

What is the issue with the HTML Standard?

Today we held our now weekly triage call (#10275) and I will post the meeting notes there in a bit. The next one is scheduled for April 25, 9am PDT. Note that this is 1 week later (per #10163) in an Americas+Europe friendly time.

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 in all WHATWG repos and we would like to invite anyone that can contribute to said issues to join us.

[lukewarlow]

Could we add WICG/sanitizer-api#226 to the agenda to discuss carving out on* names as event handlers only. So all event handler attributes should follow that naming pattern, and anything that isn't an event handler should not follow it.

[past]

Of course, I'll add it to the agenda.

[zcorpan]

I can't attend this week.

[past]

@aphillips will you have a list of issues to discuss tomorrow or should we defer this topic?

[aphillips]

@past I apologize. For various personal reasons I haven't had time to pull things together. I actually thought previously that we were scheduling for May, which makes me a dingbat. When is the next Americas/Europe call after this? Is it two weeks hence? Let's shoot for that and I promise to do better 🤦‍♂️

[past]

No worries, I'll keep deferring this topic until May 9 then.

[past]

Thank you all for attending the meeting today! Here are the notes from this meeting (the next one is at #10298):

Agenda

Attendees: Luke Warlow, Joey Arhar, Panos Astithas, David Baron, Emilio Cobos Álvarez, Dominic Farolino, Robert Flack, Mason Freed, Sanket Joshi, Brian Kardell, Yoav Weiss, Chris Wilson, Vladimir Levin, Chris Harrelson

1. Review past action items
   1. None.
2. Carryovers from last time
   1. [Addison] Joint session with the I18N WG. Addison will provide a list of topics.
      1. Deferring until May 9.
3. New topics
   1. [Yoav] Add subresource integrity support for ES modules, through importmaps
      1. Deferring for two weeks so more Mozilla and Apple folks can attend.
   2. [Luke] How to handle event handler attributes
      1. Discussion will continue asynchronously.
   3. [Panos] We are planning a joint task force between WHATWG/CSSWG/Open UI to address styleable form controls where the expertise and scope of these groups intersect. Let Panos or someone else in these groups know if you are interested in attending, so that we can add you to the calendar invites when they are ready.
   4. [Mason/Keith] Add InvokeTarget & InvokeEvent IDLs & invocation steps for Dialog & Popover
      1. Has implementer support, needs spec review.
   5. [Mason] Add popover=hint
      1. Has spec review, needs more implementer support.
      2. Emlilio thinks this sounds sensible.
   6. [Vlad] Tab Knowledge API: thoughts?
      1. People are encouraged to look into this and comment.
      2. Luke: don't service workers have the ability to do this?
      3. Vlad: not sure.
      4. Sanket: does this apply to top-level only or other same-origin things as well?
      5. Vlad: top-level frames is the use case we have in mind.
      6. Dom: top-level browsing context is perhaps the term you're looking for (this includes "auxiliary browsing contexts" which are also top-level)
   7. [Chris] Any update on Mozilla review of domfarolino's PR to define post-insertion steps?
      1. Blocked on domfarolino fixing a bug in it.
      2. Emilio described the script runner concern from the Gecko side.
      3. Dom thinks it will be a straightforward fix.
   8. [Chris] Should we minute the meetings?
      1. Panos: this would make my life easier, but I'd like to hear from the editors who aren't present.
      2. Chris W.: no concerns from my end.
      3. Dom: are the current notes insufficient?
      4. Chris H.: the value will be in not forgetting the details that were mentioned.
      5. Emilio: if we follow the CSSWG model we should expect to spend a few minutes at every meeting finding a scribe. We could use IRC and dbaron's tools in that case.
      6. Chris H.: just scribing in the existing doc will be sufficient.
      7. Luke: will these minutes be publicly accessible?
      8. Panos: I'll keep posting the minutes in the issue as usual.
      9. Chris W.: we should make sure Apple is on board with this.
      10. Chris H., Chris W. and Panos will follow up and revisit this at the next meeting.
   9. [Luke/Domenic] CloseWatcher always fire cancel events
      1. Luke and Keith reviewed it as implementers, it needs a second implementer position.
      2. Emilio will look closer at the use cases.

Action Items

1. @domfarolino will update the post-insertion steps PR to address Olli's review.
2. @chrishtr, @cwilso and @past will follow up and revisit minuting the meetings at the next meeting.
3. @emilio will look closer at the use cases for CloseWatcher always fire cancel events.