You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yesterday we held our biweekly triage call (#9308) and I will post the meeting notes there in a bit. The next one is scheduled for June 15, 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 in all WHATWG repos and we would like to invite anyone that can contribute to said issues to join us.
The text was updated successfully, but these errors were encountered:
Thank you all for attending today! Here are the notes from this meeting (the next one is at #9432):
Agenda
Attendees: Joey Arhar, Panos Astithas, Mason Freed, Brian Kardell, Anne van Kesteren, Olli Pettay, Simon Pieters
Review past action items
Domenic to write up a response for Accessibility Attribute Request focused on: is there implementer interest? And the general question of dashes in attribute names.
Done.
Google folks to collect some statistics on how often various queue lengths are overflowed around the BroadcastChannel + bfcache proposal. Anne will check if we can move forward with evicting on implementation-defined queue limit exceeded, with 2/3 support and 1 not-persuaded but not strongly objecting.
Yesterday we held our biweekly triage call (#9308) and I will post the meeting notes there in a bit. The next one is scheduled for June 15, 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 in all WHATWG repos and we would like to invite anyone that can contribute to said issues to join us.
The text was updated successfully, but these errors were encountered: