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
Today we held our biweekly triage call (#9132) and I will post the meeting notes there in a bit. The next one is scheduled for May 4, 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, we had quite a large group! Here are the notes from this meeting (the next one is at #9254):
Agenda
Attendees: Christopher Cameron, Anne van Kesteren, Olli Pettay, Vladimir Levin, Mason Freed, Brian Kardell, Shu-yu Guo, Emilio Cobos Álvarez, Joey Arhar, Panos Astithas, Robert Flack, Hannah Van Opstal, Kagami Rosylight, Simon Pieters, Khushal Sagar, Chris Harrelson, Chris Wilson
Emilio will help advise how to make the CloseWatcher spec more rigorous, and Domenic will work on upstreaming it to HTML.
Emilio hasn't gotten to this yet, carrying over.
Carryovers from last time (we largely skipped this section in favor of the new topics below, given the many new attendees specifically for this meeting)
Today we held our biweekly triage call (#9132) and I will post the meeting notes there in a bit. The next one is scheduled for May 4, 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: