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 HTML standard issue triage meeting on 5/4/2023 #9193

Closed
past opened this issue Apr 20, 2023 · 1 comment
Closed

Upcoming HTML standard issue triage meeting on 5/4/2023 #9193

past opened this issue Apr 20, 2023 · 1 comment
Labels
agenda+ To be discussed at a triage meeting

Comments

@past
Copy link

past commented Apr 20, 2023

Today we held our biweekly triage call (#9132) and I will post the meeting notes there in a bit. The next one is scheduled for May 4, 9 am PDT. Note that this is 2 weeks later in an America+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.

@past
Copy link
Author

past commented May 4, 2023

Thank you all for attending today, we had quite a large group! Here are the notes from this meeting (the next one is at #9254):

Agenda

Attendees: Christopher Cameron, Anne van Kesteren, Olli Pettay, Vladimir Levin, Mason Freed, Brian Kardell, Shu-yu Guo, Emilio Cobos Álvarez, Joey Arhar, Panos Astithas, Robert Flack, Hannah Van Opstal, Kagami Rosylight, Simon Pieters, Khushal Sagar, Chris Harrelson, Chris Wilson

  1. Review past action items
    1. Domenic to look into anchor element interactions for Modernized version of window.open() API
      1. Done.
    2. Emilio will help advise how to make the CloseWatcher spec more rigorous, and Domenic will work on upstreaming it to HTML.
      1. Emilio hasn't gotten to this yet, carrying over.
  2. Carryovers from last time (we largely skipped this section in favor of the new topics below, given the many new attendees specifically for this meeting)
    1. [Anne] Accessibility Attribute Request
      1. Didn't have time for this.
    2. [Anne] HTML cross-document encoding inheritance with bogus Content-Type charset
      1. Didn't have time for this.
    3. [Fergal] BroadcastChannel + bfcache proposal
      1. Didn't have time for this.
    4. [Brian] Update the :dir / directionality to include shadow dom (was Tests for directionality and shadow DOM)
      1. Didn't have time for this.
  3. New topics
    1. [Anne] Standardize rendering of PQ and HLG HDR image content
      1. Anne will get WebKit feedback, Emilio tagged Mozilla folks for feedback.
    2. [Khushal] Detect UA transitions on same-document navigations
      1. Related: Disabling UA transitions for same-document navigations w3c/csswg-drafts#8747
      2. Anne and Olli will provide feedback or find others to do so.
    3. [Shu] Question about new jobs for Atomics.waitAsync integration
      1. Shu will send an HTML PR after the clarifications that were discussed.
    4. [Brian] editorial: add custom element extensibility bullet 🙂
      1. Just a heads up so that people could provide feedback.

Action Items

  1. @annevk will get WebKit feedback, @emilio tagged Mozilla folks for feedback on Standardize rendering of PQ and HLG HDR image content.
  2. @annevk and @smaug---- will provide feedback for Detect UA transitions on same-document navigations or find others to do so.
  3. @syg will send an HTML PR after the clarifications that were discussed around Atomics.waitAsync integration.

@past past closed this as completed May 4, 2023
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