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 6/3/2021 #6664

Closed
past opened this issue May 7, 2021 · 5 comments
Closed

Upcoming HTML standard issue triage meeting on 6/3/2021 #6664

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

Comments

@past
Copy link

past commented May 7, 2021

Yesterday we held our monthly triage call (#6551) and I will post the meeting notes there momentarily. The next one is scheduled for June 3rd, 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
Copy link
Author

past commented Jun 5, 2021

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

Agenda

  1. Review past action items.
    1. [followup] Expand <details> for find-in-page and element fragments
      1. Fast-track process worked. Joey will redo the PR in terms of content-visibility: hidden.
    2. [followup] Specify cancelling a file upload from a file input
      1. Domenic to update the spec.
    3. [followup] Standardize a popup's condition and UI opened by window.open
      1. Mason to try out the new behavior in Chromium behind a flag, and see what the compat story looks like.
    4. [followup] Expose structuredClone
      1. Easy to implement, but not clear if this is a super high priority. Anne to summarize/ask in the issue the use cases from people who want this.
  2. [Anne] Introducing self.reportException()
    1. Easy to implement, but the need is not clear. Domenic to ask in the issue for interest from developers.
  3. [Mason] Removing navigator.plugins/mimeTypes
    1. Domenic to make the spec changes and update the issue.
  4. [Domenic] heads-up: Chrome scheduling folks are interested in interop on setTimeout() during sleep; will write up an issue for next month.
  5. [Anne] It is unclear how directionality should be inherited into Shadow DOM
    1. Skipping this time, will revisit in the future.
  6. [Domenic] The processing model for text files seems to mandate quirks mode
    1. Agreement on this and the following point. Mason to update the spec.
  7. [Domenic] Should text/media/plugin/etc documents be in quirks mode?
  8. [Anne] :read-only and :read-write selectors: Consistency and cross-UA behavior
    1. Nothing left to do, will close.

Action Items

  1. Panos to ping the meeting issue 1 or 2 weeks ahead of the meeting with calls for agenda items. Anne to create a new team (@whatwg/html-triage) in the WHATWG org.
  2. Domenic to update the spec for canceling a file upload.
  3. Mason to try out the new behavior in Chromium behind a flag, and see what the compat story looks like.
  4. Anne to summarize/ask in the issue the use cases from people who want structuredClone.
  5. Domenic to ask in the self.reportException issue for interest from developers.
  6. Domenic to make the spec changes and update the plugins/mimeTypes issue.
  7. Mason to update the spec on quirks mode for text files and media/plugin/etc documents.
  8. Anne to close the :read-only and :read-write issue.

@mfreed7
Copy link
Contributor

mfreed7 commented Jun 9, 2021

In my notes from this meeting, I also had an action item from this conversation:

I had written down that I was going to try out the new behavior in Chromium behind a flag, and see what the compat story looks like. Is that other people's recollection as well?

@domenic
Copy link
Member

domenic commented Jun 9, 2021

Yeah, I remember being impressed by your bravery in that regard :)

@past
Copy link
Author

past commented Jun 10, 2021

Sorry for missing that, meeting notes are now updated.

@mfreed7
Copy link
Contributor

mfreed7 commented Jun 10, 2021

Thanks to both of you.

See this comment: #5872 (comment)

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