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/13/2022 #8341

Closed
past opened this issue Sep 30, 2022 · 4 comments
Closed

Upcoming HTML standard issue triage meeting on 10/13/2022 #8341

past opened this issue Sep 30, 2022 · 4 comments
Labels
agenda+ To be discussed at a triage meeting

Comments

@past
Copy link

past commented Sep 30, 2022

Yesterday we held our biweekly triage call (#8250) and I will post the meeting notes there in a bit. The next one is scheduled for October 13, 1 am PDT, per #8106. Note that this is 2 weeks later in a Europe+APAC 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 past added the agenda+ To be discussed at a triage meeting label Sep 30, 2022
@charan-happy
Copy link

I am Interested in it past . Requesting you to allow me to next call.

@past
Copy link
Author

past commented Oct 11, 2022

I have added you to the invite.

@past
Copy link
Author

past commented Oct 11, 2022

Hey @whatwg/html-triage, the agenda for this meeting is still pretty sparse, so please tag any issues/PRs that should be discussed on Thursday.

@past
Copy link
Author

past commented Oct 13, 2022

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

Agenda

  1. Review past 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 Olli.
      1. Emilio pinged, probably this week we'll get the tests?
    2. Domenic needs to do the spec work for Define timing of focus fixup rule precisely when triggered by style changes.
      1. Domenic still has not done this.
      2. Let's let it drop off the action items list for now.
    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.
      1. Done!
    4. Joey will land a change to change Chromium's behavior around Event bubbling on disabled form elements.
      1. Joey said he would try to land it, not sure if he did?
    5. Emilio will add a spec change for HTMLOptionsCollection length setter should specify what happens when you go over the option limit.
      1. People on the call (which does not include Mason or Emilio today) think 100,000 is also fine, but we'll wait for Emilio.
      2. Also nobody should do this. Official HTML triage call position.
  2. Carryovers from last time
  3. New topics
    1. [Mike] Revisit Is a general Script: editor a good idea?
      1. Couldn't find anything about the Link header being an antipattern, at least in TAG.
      2. Some discussion about these types of headers from WebKit being problematic for serializability (i.e. save-to-disk). Also a problem with Link: rel=stylesheet.

Action Items

None

@past past closed this as completed Oct 13, 2022
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

2 participants