Upcoming WHATNOT meeting on 6/13/2024

[past]

What is the issue with the HTML Standard?

Today we held our now weekly triage call (#10381) and I will post the meeting notes there in a bit. The next one is scheduled for June 13, 1am PDT. Note that this is 1 week later in an APAC+Europe friendly time.

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

@whatwg/triage the agenda doesn't have any new items for this meeting, but there are a few carry overs to go through. Please tag any new issues that should be discussed.

[saschanaz]

Today I had no issue with Google Meet and was able to join and do my first scribe. Next one is ... @past hasn't filed one! So I did, #10408.

Agenda

Attendees: olli, annevk, mike smith, kagami, zcorpan
Scribe: kagami

1. Review past action items
   1. Emilio to collect compat data and propose a spec PR for min/max in [forms] Number input intrinsic size.
      1. Deferred for next time as Emilio is not here.
   2. Chris will ping Mustafa for a Chrome update on HTTPS upgrades proposal.
      1. Done.
   3. Ben will ping Emilio for Gecko’s take on the contentvisibilityautostatechange event PR.
      1. Deferred for next time as Emilio is not here.
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. Deferred for next time as Emilio is not here.
   2. Revisit invoketarget naming discussion. Concrete naming proposal is commandfor/command.
   3. New topics
      1.None.

Action Items

(empty)

Minutes

[olli] now bit unclear that what people are proposing - it’s commandfor
[anne] maybe command / for would work
[simon] if we want to make this support FACE than it’s a reason to make this global
[olli] I like that there’s no implicit command, you need to say what command you want to trigger

(some discussion about toggling)

[anne] it’s bad that people would need to use type=button to make it work, as defaults to a submit button inside a form. Maybe make it button by default when command attribute exists
[olli] trying to find a concrete example in gecko that clicking a button changes something else and then the label of itself
[simon] the fullscreen button in the hamburger menu does
[olli] I’ll check how it’s implemented
[anne] we should make sure the accessibility mapping be defined when HTML PR happens
[simon] inline a11y mapping into the main standard?
[anne] but it has its own spec, maybe add a checkbox on a PR

[past]

Thank you for capturing and posting the meeting notes @saschanaz!