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 8/10/2023 #9591

Closed
past opened this issue Aug 8, 2023 · 1 comment
Closed

Upcoming HTML standard issue triage meeting on 8/10/2023 #9591

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

Comments

@past
Copy link

past commented Aug 8, 2023

Apologies for filing this issue so late, but I was on vacation. Two weeks ago we held our biweekly triage call (#9515) and I will post the meeting notes there in a bit. The next one is scheduled for August 10, 4pm PDT. Note that this is 2 weeks later in an APAC+America 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 Aug 10, 2023

Thank you all for attending today! Here are the belated notes from this meeting (the next one is at #9598):

Agenda

Attendees: Joey Arhar, Panos Astithas, Marcos Caceres, Mason Freed, Vladimir Levin, Olli Pettay, Michael Smith

  1. Review past action items
    1. Brian will address review feedback on Update the :dir / directionality to include shadow dom.
    2. Yi will review Reference even more baseline concepts in CSS Inline Layout.
  2. Carryovers from last time
    1. None.
  3. New topics
    1. [Vladimir] Proposal: fire an event before the first rendering opportunity after activation
      1. Discussion about the developer ergonomics of adding a new event or using rAF for this. A new event provides more info via an event parameter and less code for handling.
      2. Discussed the interaction between a reveal event and renderblocking, as well as how Firefox could implement this.
      3. Marcos will find someone from WebKit to provide feedback.
      4. Vladimir will comment with an example of a rAF-based solution.

Action Items

  1. @marcoscaceres will find someone from WebKit to provide feedback on the Proposal: fire an event before the first rendering opportunity after activation.
  2. @vmpstr will comment on the proposal above with an example of a rAF-based solution.

@past past closed this as completed Aug 10, 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