-
Notifications
You must be signed in to change notification settings - Fork 2.6k
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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 2024-07-18 #10471
Comments
We're looking to implement If possible I'd like to be invited to the call to discuss #1918 and what recommendations there are for our implementation. |
Thank you all for attending the meeting today and special thanks to Keith Cirkel for copiously taking meeting notes! Here are the notes from this meeting (the next one is at #10496): AgendaAttendees: Luke Warlow, Panos Astithas, David Baron, Keith Cirkel, Emilio Cobos Álvarez, Sanket Joshi, Andrew Kaster, Una Kravets, Schalk Neethling, Olli Pettay, Ajay Rahatekar, Noam Rosenthal, Kagami Rosylight, Benjamin VanderSloot, Anne van Kesteren, Yoav Weiss, Chris Harrelson, Joey Arhar
Action Items
MinutesTopic: Input type color alpha & p3 Panos: Welcome. Reviewing past action items. First; Joey? Topic: Tie in AbortControllers with CustomElements Keith: Everyone happy with the current direction? Topic: Severing a document's opener relationship regardless of origin Yoav: Missed last discussion. If I read correctly there are a couple of open questions for me. One; potentially want noopener that doesn't allow popups in order to make it useful for bfcache. Not objecting but seems something we can add on as a separate PR as an extra value. Similarly relationship with COAP - we can have a more conservative approach not effecting cross origin isolated state. Expand to scenarios, backward compatible change. Haven't heard back from others. Wondering if we can push this forward if folks agree these questions can be dealt with later. Topic: redact location.ancestorOrigins according to Referrer Policy keith: i dont think this is my issue? ** Topic [Proposal] Invoker Buttons - allowing popover/dialog and more to be invoked without JS** keith: anne mentioned that commandevent has a proeprty invoker which refers to the button, is not the target its the related target but can't be called that, i think we want to rename this to something else. i dont think it can be invoker or command. we could call it button but i dont know how that jives. luke suggested commander. im easy with whatever name. Anne: This is another concern on legacy algorithms. DOM parsing is in a bad state. Panos: In that case we're out of topics. Anything else? Joey: Select element improvements - UA stylesheet changes, I want to propose a lot of them. Where should we be talking about it? We have the shared forms meeting, css, and this. UA style changes should be in CSS or joint? If we resolve there is it okay to go into HTML? |
What is the issue with the HTML Standard?
Today we held our weekly triage call (#10463) and I will post the meeting notes there in a bit. The next one is scheduled for July 18, 9am PDT. Note that this is 1 week later in an Americas+Europe friendly time.
People interested in attending the next call please respond here or reach out privately to @past, @cwilso 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: