-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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 WHATNOT meeting on 3/14/2024 #10200
Comments
As noted in #10156 (comment) I believe there is a plan to discuss w3c/csswg-drafts#9951 at this meeting. |
Also a note for those not in North America: 9am California time (PDT) is an hour earlier than it was a week before, since most of the US and Canada have switched to summer time. |
Thank you all for attending the meeting today! Here are the notes from this meeting (the next one is at #10205): AgendaAttendees: Luke Warlow, Tab Atkins-Bittner, David Baron, Emilio Cobos Álvarez, Brecht De Ruyte, Elika Etemad, Mason Freed, Chris Harrelson, Sanket Joshi, Tim Nguyen, Ryosuke Niwa, Simon Pieters, Noam Rosenthal, Alan Stearns, Miriam Suzanne, Anne van Kesteren, Chris Wilson, Dan Veditz, Keith Cirkel, Vladimir Levin
Action Items
|
This adds the ::details-content pseudo-element as resolved in: 1. w3c#9879 (comment) 2. whatwg/html#10200 (comment) / w3c#9951 (comment) 3. w3c#9879 (comment) and uses the definition added in w3c#10083.
This adds the ::details-content pseudo-element as resolved in: 1. w3c#9879 (comment) 2. whatwg/html#10200 (comment) / w3c#9951 (comment) 3. w3c#9879 (comment) and uses the definition added in w3c#10083.
This adds the ::details-content pseudo-element as resolved in: 1. #9879 (comment) 2. whatwg/html#10200 (comment) / #9951 (comment) 3. #9879 (comment) and uses the definition added in #10083.
What is the issue with the HTML Standard?
Last week we held our biweekly triage call (#10156) and I will post the meeting notes there in a bit. The next one is scheduled for March 14, 9am PST. Note that this is 1 week later in an America+Europe friendly time, per #10163 and last week's meeting consensus.
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: