Upcoming WHATNOT meeting on 2024-08-22

[past]

What is the issue with the HTML Standard?

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

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

Thank you all for attending the meeting today and special thanks to Chris Harrelson for taking meeting notes! Here are the notes from this meeting (the next one is at #10574):

Agenda

Attendees: Panos Astithas, Chris Harrelson, Sanket Joshi, Olli Pettay, Ajay Rahatekar, Joey Arhar
Scribe: Chris Harrelson

1. Review past action items
   1. Anne, Olli to review <select> proposal for stage 2
      1. Olli: ongoing, but no concerns with stage 2 entrance. Consensus was to wait for WebKit's feedback by next week, given this is the first time we're considering a stage 2 entrance.
   2. Olli, Mason to find someone to review Add the autocorrect attribute.
      1. Mason reviewed.
      2. Olli asked makoto
2. Carryovers from last time
   1. None.
3. New topics
   1. [Chris] HTML forms do not support the PUT, PATCH and DELETE methods
      1. Carry over so that Alex can present.
   2. [Anne] Allow notifications and actions to specify a navigable URL
      1. Kagami is looking into this from Mozilla and Chris will find someone from Chromium to take a look.
   3. [Chris] Add popover=hint
      1. Olli will ping Emilio.

Action Items

1. @chrishtr will find someone from Chromium to take a look at allow notifications and actions to specify a navigable URL.
2. @smaug---- will ping @emilio for add popover=hint.

Minutes

Past action items.
Olli: still looking at the spec. Should be fine for Stage 2.
Panos: stage 2 needs a draft spec and a roughly right approach, and no big issues. From that perspective does it seem ok?
Olli: yes seems ok and no big issues.
Panos: would be good to double-check with Webkit representatives, but let's move to Stage 2 if they don't raise big concerns by the next meeting.
Olli: one dimension that hasn't been reviewed by Mozilla is accessibility. Will need to do that
Chris: a11y is going to be handled by Aaron and Scott
Joey: some stuff is mentioned in the spec
Sanket: we are actively working on the a11y implementation in Chromium
Chris: Olli do you have a contact person at Mozilla for a11y?
Olli: that would be James Teh (jteh@mozilla.com)
Panos: next topic: autocorrect attribute. Mason reviewed, Olli asked someone to review.
Panos: next topic: allow notifications and actions to specify a navigable URL
Olli: might be bad to always open a new tab when clicking on a notification. If you're already in the site then it might not be good to open a new window/tab. Want to ask Anne for use cases.
Olli: Kagami is looking into it.
Panos: who from Chromium can provide feedback?
Chris: will take an action item to find out.
Olli: lots of history in the PUT/PATCH/DELETE discussion!
Chris: Olli did anyone from Mozilla get a chance to look at popover=hint?
Olli: Emilio left one comment last week. Will ping him to ask for an update.

[annevk]

Consensus was to wait for WebKit's feedback by next week, given this is the first time we're considering a stage 2 entrance

Perhaps this needs to be clarified, but I would kinda expect this to be the norm if people have indicated they are going to take a look and haven't shared their findings yet.

[past]

Consensus was to wait for WebKit's feedback by next week, given this is the first time we're considering a stage 2 entrance

Perhaps this needs to be clarified, but I would kinda expect this to be the norm if people have indicated they are going to take a look and haven't shared their findings yet.

I will bring this point up in the next meeting.