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 10/27/2022 #8385

Closed
past opened this issue Oct 13, 2022 · 1 comment
Closed

Upcoming HTML standard issue triage meeting on 10/27/2022 #8385

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

Comments

@past
Copy link

past commented Oct 13, 2022

Today we held our biweekly triage call (#8341) and I will post the meeting notes there in a bit. The next one is scheduled for October 27, 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 and we would like to invite anyone that can contribute to said issues to join us.

@past
Copy link
Author

past commented Oct 27, 2022

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

Agenda

  1. Review past action items

    1. None
  2. Carryovers from last time

    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 Olli.
      1. Done, tests and everything.
    2. Joey will land a change to change Chromium's behavior around Event bubbling on disabled form elements.
      1. Change landed, likely shipping in Chrome M109.
  3. New topics

    1. [Dominic] autocomplete attribute for street-address details
      1. Dominic collected a lot of data. Looking for engineers from other browsers to join a half day workshop to dig deeper into the problem. Ollie and Emilio to find a Firefox rep, Anne to find a Safari rep.
    2. [Emilio] Make the focus fixup rule more explicit
      1. Anne will find the WebKit experts and confirm that they are OK with the timing proposal. Mason or Joey to add feedback on what Blink is using for removal.
    3. [Anne] Align with DOM DocumentFragment adoption changes
      1. Didn't have time for this.
    4. [Joey] New feature proposal: Popup API
      1. Didn't have time for this.

Action Items

  1. @smaug---- and @emilio to find a Firefox rep, @annevk to find a Safari rep for a longer discussion of autocomplete attribute for street-address details.
  2. @annevk will find the WebKit experts and confirm that they are OK with the timing proposal to make the focus fixup rule more explicit. @mfreed7 or @josepharhar to add feedback on what Blink is using for removal.

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