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 4/1/2021 #6481

Closed
past opened this issue Mar 11, 2021 · 3 comments
Closed

Upcoming HTML standard issue triage meeting on 4/1/2021 #6481

past opened this issue Mar 11, 2021 · 3 comments
Labels
agenda+ To be discussed at a triage meeting

Comments

@past
Copy link

past commented Mar 11, 2021

Last week we weld our monthly triage call (#6371) and the next one is scheduled for April 1st, 9 am PST. 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 and we would like to invite anyone that can contribute to said issues to join us.

@annevk
Copy link
Member

annevk commented Mar 23, 2021

With regards to action items, note that @rniwa elaborated on the alternative approach to the imperative shadow DOM distribution API here: #3534 (comment).

Also, I'm taking time off for two weeks so I'll miss this meeting.

@annevk annevk added the agenda+ To be discussed at a triage meeting label Mar 23, 2021
@past
Copy link
Author

past commented Apr 1, 2021

Thanks everyone for attending! Here are the notes from the meeting (next one is at #6551):

Agenda

  1. Review past action items
    1. <popup>
      1. Dialog should be better-behaved on misuse, probably
      2. [Popup] Invoking popups from custom elements with script vs popup attribute
        1. Olli to file issues against popup spec.
        2. Melanie to follow up with the rest of the action items from the last meeting on popup.
    2. BF cache
    3. Imperative Slot API, rniwa@ proposal
      1. Agreement on the proposal. Merge after this last issue is implemented.
    4. Fast review process
      1. Try the process on the imperative slot API
  2. New items
    1. Declarative Shadow DOM getInnerHTML() API. Proposal to change the naming and parameters a bit, 1) to align with selection API (getComposedInnerHTML) and 2) to be a bit more agnostic to open vs. closed shadow roots (shadowRoots vs. closedRoots).
      1. Punting for next time, since Anne has the context.
    2. Apply text-align: match-parent to the option element in the UA stylesheet
      1. Emilio to look into current behavior.
    3. Output element value/defaultValue/reset() is not interoperable
      1. Mason to look into whether we need use counters or can just fix. Sean or Emilio to look into the Firefox issue.
    4. Consider not normalizing form entries during construction of the entry list
      1. Olli to post a summary of where Firefox is today and Mason to think about compatibility concerns. Discuss further next time.
    5. Add XML declaration encoding sniffing
      1. Mason to look into Chromium implementation. Olli to ask Henri to clarify his position.
    6. Dialog moving focus to previously focused element; Move focus to dialog itself
      1. Sean to get accessibility folks to describe the problematic behavior in Chromium. Melanie to ask Microsoft accessibility folks for input.

Action Items

  1. Olli to file issues against popup spec.
  2. Melanie to follow up with the rest of the AIs from last time on popup.
  3. Domenic to apply the fast review process to the imperative slot API.
  4. text-align: match-parent: Emilio to look into currently implemented behavior in Firefox/Chromium.
  5. Mason to look into whether we need use counters for the output element or can just fix it. Sean or Emilio to look into the Firefox issue.
  6. Olli to post a summary of where Firefox is today with normalizing form entries and Mason to think about compatibility concerns. Discuss further next time.
  7. Mason to look into Chromium implementation for XML declaration encoding sniffing. Olli to ask Henri to clarify his position.
  8. Sean to get accessibility folks to describe the problematic behavior in Chromium. Melanie to ask Microsoft accessibility folks for input.

@past past closed this as completed Apr 1, 2021
@mfreed7
Copy link
Contributor

mfreed7 commented Apr 2, 2021

Thanks - great meeting. There is one action item missing:

  1. Mason to own updating the Imperative Slot API PR, with the rough consensus proposal. This will be the first test run of the “Fast review process”.

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

3 participants