Upcoming WHATNOT meeting on 5/30/2024

[cwilso]

What is the issue with the HTML Standard?

Today we held our now weekly triage call (#10352) and I will post the meeting notes there in a bit. The next one is scheduled for May 30, 4pm PDT. Note that this is 1 week later (per #10163) in an Americas+APAC friendly time.

People interested in attending the next call please respond here or reach out privately to @past, 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.

[past]

Thank you all for attending the meeting today and special thanks to Joey Arhar for copiously taking meeting notes! Here are the notes from this meeting (the next one is at #10381):

Agenda

Attendees: Michael Smith, Joey Arhar, Tantek Celik, Sanket Joshi, Benjamin VanderSloot, Domenic Denicola, Chris Harrelson, Panos Astithas
Scribe: Joey Arhar

1. Review past action items
   1. Mason to collect options on invokerbutton naming, others to weigh in to add options via emoji response, possible developer survey of options after. Focus on target name as primary common case. Sticking with two attributes.
      1. Done.
   2. Action: Anne to review the Introduce DOM post-connection steps PR for editorial content. Dom to file a new issue and refer to this PR.
      1. Carry over.
   3. Action: Emilio to review all of popover-hint
      1. Done.
2. Carryovers from last time
   1. Emilio to work on pulling out the common points for iframe throttling into the issue about Consider improving interoperability of <iframe> throttling margins, and maybe a spec PR.
      1. Carry over
   2. Rakesh will write a PR to have a more concrete conversation on The dropEffect column in the Drag and Drop events summary table should clarify it represents default values.
   3. Rakesh will compare the platforms-specific behavior and come up with a concrete proposal for Drag and drop spec allows multiple values for dropEffect which might cause browsers to behave differently and How should UAs handle web authors setting dropEffect values?
      1. Rakesh and team working on these two issues and will add them back to the agenda when ready.
3. New topics
   1. [Mason] Add anchor attribute
      1. Ben to ask Emilio for Gecko's perspective. Anne and Tim to comment from the WebKit side.

Action Items

1. @bvandersloot-mozilla to ask @emilio for Gecko's perspective on anchor attribute. @annevk and @nt1m to comment from the WebKit side.

Minutes

• collecting options on invokerbutton naming
  • panos: anything further to add to this? sounds like we're good
• anne to review dom's PR
  • panos: i haven't seen this happen yet. still where we left it. Does anyone have context or should I carry it over?
  • chris: anne said he would be able to get to it this week
  • panos: I'll carry it over so we can discuss it next week and ping anne
• emilio popover hint
  • panos: i see that he left comments there. any further questions to discuss here?
  • panos: i see mason already replied to some of that
• emilio to work on pulling out the common points…
  • panos: does anyone have further context on this or should i carry it over?
  • panos: sounds like a carryover
• rakesh to write a pr for a more concrete…
  • panos: maybe sanket has an update?
  • sanket: yeah the team is working on it and doing some research to get back with a concrete proposal. once that's done they'll put it back on the agenda
  • panos: is that the case for the next one as well?
  • sanket: yes
• add anchor attribute
  • Joey: Looking to merge if there are no more objections
  • Joey: Mozilla and Apple can look into it
  • Ben: I will ask emilio to look into it
  • Panos: Domenic anything else missing here?
  • Domenic: this is blocked on implementer interest

[annevk]

I left a review in whatwg/dom#1261. I was hoping to be reminded by someone filing the follow-up issue that was discussed, but that didn't happen. But this issue reminded me. Thanks!