Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upcoming WHATNOT meeting on 2024-08-15 #10556

Closed
past opened this issue Aug 13, 2024 · 1 comment
Closed

Upcoming WHATNOT meeting on 2024-08-15 #10556

past opened this issue Aug 13, 2024 · 1 comment
Labels
agenda+ To be discussed at a triage meeting

Comments

@past
Copy link

past commented Aug 13, 2024

What is the issue with the HTML Standard?

Last week we held our weekly triage call (#10538) and I will post the meeting notes there in a bit. The next one is scheduled for August 15, 9am PDT. Note that this is 1 week later in an Americas+Europe 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 past added the agenda+ To be discussed at a triage meeting label Aug 13, 2024
@past
Copy link
Author

past commented Aug 15, 2024

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

Agenda

Attendees: Joey Arhar, Panos Astithas, David Baron, Keith Cirkel, Emilio Cobos Álvarez, Mason Freed, Brian Kardell, Schalk Neethling, Olli Pettay, Anne van Kesteren, Chris Wilson, Di Zhang, Peter Van der Beken
Scribe: Chris Wilson

  1. Review past action items
    1. Olli to report back with more detail on what he found weird in the import maps processing model.
      1. Still todo.
    2. Mozilla folks to decide whether they're happy with stage 2 for <select>. (And Apple folks should as well, but they weren't on the call.)
      1. Olli thinks this is fine for stage 2. Anne will take a look before next week's meeting and we'll check in again.
  2. Carryovers from last time
    1. None.
  3. New topics
    1. [Anne] Add the autocorrect attribute
      1. Olli will find someone to review the PR. Mason will review the PR or find someone else.
    2. [Anne] Update 2D canvas color serialization
      1. Consensus in the room to move forward with the proposal.
    3. [Panos] WHATUP meeting at TPAC

Action Items

  1. @annevk, @smaug---- to review <select> proposal for stage 2
  2. @smaug----, @mfreed7 to find someone to review Add the autocorrect attribute. Done.

Minutes

Panos: couple of items from last time. Import maps still to do. <select> issue moving to stage 2?
Joey: given the defn of stage 2, I think we're here, but wanted to check in. Moz/Apple?
Anne: I haven't had enough time to look at the draft spec; generally supportive, but want to have a look.
Olli: +1. Mostly okay, but want to take a closer look.
Panos: will push off to next meeting
Joey: also opened a PR for the parser changes
Anne: I left some feedback; some of the changes made were not reflected in the commit message; should make sure to add processing model changes to the commit message.
Panos: On to autocorrect attribute.
Anne: Apple proposed this in 2020, I pushed a PR in 2022 but then lost track of it over the holidays. Domenic reviewed it and found one thing. On the processing model, whether empty strings are special or not.
Olli: Moz doesn't have an implementation but makoto(?) was interested and asked about it recently.
Anne: no rush, but it would be nice to get a look on it.
Mason: haven't reviewed yet, as an editing issue will ask someone else to take a look.
Panos: on to 2d canvas color serialization.
Anne: At some point we enlarged the number of callers that the canvas setter accepts to basically accept any kind of CSS value but didn't update the getter for serialization. This is more like a bug fix, but there are some implications in the choices you can make for serialization. I chose to align mostly with what Safari and Chrome do; Firefox still seems to mostly output hex values.
Emilio: I think serializing to a modern color space seems fine.
Anne: together with the input type color changes I'm making this will remove color serialization from HTML and it will belong to CSS.
Emilio: Don't we still have BGCOLOR parsing
Anne: Sounds like we have implementer agreement? (no dissent)
Panos: Any other topics? (no) At TPAC, we have WHATUP meeting, set of sessions. Was hoping to post an issue with a sparse agenda prior to this meeting, but didn't get to it.
Anne: I have two groups we should reach out to meet with -
Panos: We're meeting with CSS and a separate meeting with CSS+OpenUI. Also Web Performance, APA and I18n.
Anne: I was going to say APA and i18n. Addison's issues, and area attribute reflection for APA
Keith: ARIA WG is working through that
Anne: (some concerns)
Panos: sounds like we'll have a good meeting at TPAC. Thanks all!

@past past closed this as completed Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agenda+ To be discussed at a triage meeting
Development

No branches or pull requests

1 participant