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 1/26/2023 #8723

Closed
past opened this issue Jan 12, 2023 · 3 comments
Closed

Upcoming HTML standard issue triage meeting on 1/26/2023 #8723

past opened this issue Jan 12, 2023 · 3 comments
Labels
agenda+ To be discussed at a triage meeting

Comments

@past
Copy link

past commented Jan 12, 2023

Today we held our biweekly triage call (#8614) and I will post the meeting notes there in a bit. The next one is scheduled for January 26, 1 am PST. Note that this is 2 weeks later in an APAC+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 past added the agenda+ To be discussed at a triage meeting label Jan 12, 2023
@nicolo-ribaudo
Copy link
Contributor

Hello! Is this call open to anyone? I'd like to join to take part in the discussion for #7233.

@past
Copy link
Author

past commented Jan 25, 2023

Hi @nicolo-ribaudo, if you can send me (or anyone else on the call) your email address I will add you to the invite. I'm pastith at GMail and Twitter (my DMs are open).

@past
Copy link
Author

past commented Jan 26, 2023

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

Agenda

  1. Review past action items
    1. Panos to bring up this meeting slot next time with Anne to see if we can have someone from Apple participate.
      1. Panos is absent today, but hopefully Anne can comment on Apple participation in the APAC+America friendly meeting.
        1. Anne will ask around. Maybe Marcos!?
    2. Domenic/Mason/Joey will take a look at Details and summary styles don't match implementations.
      1. Domenic commented.
      2. Still on Mason/Joey to confirm. But we should probably move ahead. We have tests already.
      3. Related issue: how to style the anonymous summary? We could have a selector or we could have prose.
      4. AI(emilio): send a spec PR to match implementations. Use prose for anonymous summary for now.
    3. Joey will make the agreed upon changes on the Popover API proposal and Domenic will comment on the new thread.
      1. Done. Domenic raised some additional points for discussion in his comment.
      2. Status: We're happy with the event setup (and everything else) but the spec text just hasn't been reviewed. Anne has put it in his calendar for tomorrow.
  2. Carryovers from last time
    1. Emilio to investigate :user-valid and :user-invalid
      1. Still to-do
    2. [Anne] Align with DOM DocumentFragment adoption changes
      1. Anne needs to look at it again and either suggest pushing through, or find an alternative path. Let's keep carrying this over to the next meeting.
  3. New topics
    1. [Olli] Session history entries list is assumed to be unlimited in size
      1. AI(Olli): to suggest some changes on the issue, Domenic can help to get them written up into a spec PR if necessary
      2. Anne to check if WebKit has any opinions. Apparently they changed their limit from 50 to 100 at some point!
      3. Specific problem: pushState() x50, reload(), pushState() x50. Since reload is async, what happens? (Gecko ignores the reload.)
    2. [Domenic] Implement dialog initial focus proposal
      1. AI(Olli) to take a look for Mozilla
        1. Now done: New dialog initial focus algorithm mozilla/standards-positions#734 (comment)
      2. AI(Domenic + Anne) to work out the new example text, but WebKit is generally supportive.
    3. [Anne] CSS and JSON module scripts and CSP
      1. AI(Domenic) to check with the V8 team on their opinion on "is import assertions a bad name?" and "are we OK changing the syntax?". Ideally get the feedback before Monday next week.
    4. [Domenic] <input type="time"> : Time vs. duration
      1. Didn't get to this.

Action Items

  1. @mfreed7 / @josepharhar will take a look at Details and summary styles don't match implementations. @emilio will send a spec PR to match implementations. Will use prose for anonymous summary for now.
  2. @annevk will review the Popover API proposal.
  3. @smaug---- will suggest some changes on the Session history entries list is assumed to be unlimited in size issue, @domenic can help to get them written up into a spec PR if necessary. @annevk to check if WebKit has any opinions.
  4. @domenic and @annevk will work out the new example text for Implement dialog initial focus proposal.
  5. @domenic will check with the V8 team on their opinion on "is import assertions a bad name?" and "are we OK changing the syntax?".

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