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 9/29/2022 #8250

Closed
past opened this issue Sep 1, 2022 · 1 comment
Closed

Upcoming HTML standard issue triage meeting on 9/29/2022 #8250

past opened this issue Sep 1, 2022 · 1 comment
Labels
agenda+ To be discussed at a triage meeting

Comments

@past
Copy link

past commented Sep 1, 2022

Today we held our biweekly triage call (#8208) and I will post the meeting notes there in a bit. The next one is scheduled for September 29, 4 pm PDT, per #8106. Note that this is 4 weeks later in an APAC+America friendly time. We will be skipping the meeting of September 15 as it conflicts with TPAC.

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 and we would like to invite anyone that can contribute to said issues to join us.

@past
Copy link
Author

past commented Sep 30, 2022

Thanks everyone for attending! Here are the notes from this meeting (the next one is at #8341):

Agenda

  1. Review past action items
    1. Emilio will make sure the Gecko patch for focus delegate code seems wrongly only looking at children includes enough test coverage.
      1. Emilio will ping the patch author or take over and send the patch to Olli.
    2. Anne to check with WebKit canvas people, post an update on Rendering of "bitmaprenderer"-backed canvas, ideally including a concrete proposal for a spec change everyone can converge on.
      1. No progress.
    3. Domenic to do spec work for Define timing of focus fixup rule precisely when triggered by style changes, Emilio to update tests.
      1. The tests are ready to land, Domenic needs to do the spec work.
      2. Tests at https://phabricator.services.mozilla.com/D156219.
  2. Carryovers from last time
    1. [Domenic] Define link processing for prefetch
      1. Made progress at TPAC, will continue discussing in the issue.
  3. New topics
    1. [Domenic] Is a general Script: header a good idea?
      1. The consensus was to use separate headers.
    2. [Emilio] Intersection observer and mark paint timing steps should run after (or during) "update the rendering", not before
      1. Emilio will send a PR to make it so, including upstreaming ResizeObserver.
    3. [Olli] Event bubbling on disabled form elements
      1. Joey will land a change to change Chromium's behavior.
    4. [Domenic] Iframes should inherit the base URL of the parent document in some cases
      1. Emilio notes that Gecko does srcdoc dynamically, but thinks changing this should be fine.
      2. Domenic will continue work on this.
    5. [Emilio] Let's talk about HTMLOptionsCollection length setter should specify what happens when you go over the option limit!
      1. Emilio will add a spec change for this, consensus was to align on WebKit's behavior (clamp the value and warn in the console).

Action Items

  1. @emilio will ping the patch author for focus delegate code seems wrongly only looking at children or take over and send the patch to @smaug----.
  2. @domenic needs to do the spec work for Define timing of focus fixup rule precisely when triggered by style changes.
  3. @emilio will send a PR to make Intersection observer and mark paint timing steps run after (or during) "update the rendering", not before, including upstreaming ResizeObserver.
  4. @josepharhar will land a change to change Chromium's behavior around Event bubbling on disabled form elements.
  5. @emilio will add a spec change for HTMLOptionsCollection length setter should specify what happens when you go over the option limit.

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