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 5/6/2021 #6551

Closed
past opened this issue Apr 1, 2021 · 5 comments
Closed

Upcoming HTML standard issue triage meeting on 5/6/2021 #6551

past opened this issue Apr 1, 2021 · 5 comments
Labels
agenda+ To be discussed at a triage meeting

Comments

@past
Copy link

past commented Apr 1, 2021

Today we weld our monthly triage call (#6481) and I will post the meeting notes there in a bit. The next one is scheduled for May 6th, 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.

@past past added the agenda+ To be discussed at a triage meeting label Apr 1, 2021
@mfreed7
Copy link
Contributor

mfreed7 commented Apr 2, 2021

Let's please add #6003 to the next agenda. Thanks!

@domenic
Copy link
Member

domenic commented Apr 2, 2021

@mfreed7 I've added the label and also given you "triage" permissions so that (if I understand GitHub ACLs right) you can add labels with impunity now :)

@annevk
Copy link
Member

annevk commented Apr 13, 2021

Note that @mfreed7 should already have triage access as he's part of the triage team.

@mfreed7
Copy link
Contributor

mfreed7 commented Apr 23, 2021

Thanks for both comments. I can confirm that I do (and maybe did) have the ability to add labels.

@past
Copy link
Author

past commented May 7, 2021

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

Agenda

  1. Quick run-through of old action items from prior meetings
  2. [Chris] Review results of "fast-review" for imperative shadow DOM distribution
    1. Pilot was successful, maybe item 11 is a good next candidate. Other successful cases were color profiles, etc.
  3. [followup] Apply text-align: match-parent to the option element in the UA stylesheet
    1. Progress was made, agreed to remove the label.
  4. [followup] Output element value/defaultValue/reset() is not interoperable
    1. Progress was made, agreed to remove the label. Emilio to respond to Anne.
  5. [followup] Consider not normalizing form entries during construction of the entry list
    1. Agreement to land the spec and WPT, Mason to review.
  6. [followup] Add XML declaration encoding sniffing
    1. This can land.
  7. [Anne] Standardize a popup's condition and UI opened by window.open
    1. There are two questions to consider here:
      1. When does window.open() create a "popup"? https://arai-a.github.io/window-open-features/#IsPopup (suggest to align with Safari)
        1. Mason to look into this, there is concern for website breakage due to browser sniffing
      2. What do the BarProp properties return there: Further BarProp cleanup #4431 (comment) (suggest to align with Chrome)
        1. Mildly risky? Firefox agrees to change.
      3. Safari comment: Standardize a popup's condition and UI opened by window.open #5872 (comment)
  8. [Domenic] Specify cancelling a file upload from a file input
    1. Anne to discuss with Firefox engineers, Domenic to think about the <select> similarities.
  9. [Anne] Expose structuredClone
    1. Common developer request, agreed that it's a good addition. Async vs. sync API is still an open question. Chris to follow up with Surma about developer interest.
  10. [Mason] Custom Elements: deferred upgrade until displayable
    1. Everyone to read through and leave comments. Mason and Chris to leave a comment on timing trickiness.
  11. [Domenic] Expand <details> for find-in-page and element fragments
    1. Fast track this, Anne and Domenic to follow up

Action Items

  1. Progress was made on Apply text-align: match-parent to the option element in the UA stylesheet #6538, agreed to remove the label.
  2. Progress was made on Output element value/defaultValue/reset() is not interoperable #6516, agreed to remove the label. Emilio to respond to Anne.
  3. Agreement to land the spec and WPT changes in Consider not normalizing form entries during construction of the entry list #6469, Mason to review.
  4. Agreement to land XML declaration encoding sniffing.
  5. Mason to look into when window.open() creates a "popup", there is concern for website breakage due to browser sniffing.
  6. Anne to discuss Specify cancelling a file upload from a file input #6376 with Firefox engineers, Domenic to think about the <select> similarities.
  7. Expose structuredClone is a common developer request, there was agreement that it's a good addition. Async vs. sync API is still an open question. Chris to follow up with Surma about developer interest.
  8. Everyone to read through Custom Elements: deferred upgrade until displayable #6480 and leave comments. Mason and Chris to leave a comment on timing trickiness.
  9. Use the fast track process for Expand <details> for find-in-page and element fragments #6466, Anne and Domenic to follow up.

@past past closed this as completed May 7, 2021
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

4 participants