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 8/4/2022 #8089

Closed
past opened this issue Jul 8, 2022 · 1 comment
Closed

Upcoming HTML standard issue triage meeting on 8/4/2022 #8089

past opened this issue Jul 8, 2022 · 1 comment
Labels
agenda+ To be discussed at a triage meeting

Comments

@past
Copy link

past commented Jul 8, 2022

Yesterday we held our monthly triage call (#7981) and I will post the meeting notes there in a bit. The next one is scheduled for August 4, 9 am PDT. 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 Aug 5, 2022

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

Agenda

  1. Review past action items
    1. Eric to reply to every unresolved comment on the PR for directionality in the shadow DOM.
      1. Eric replied to all and resolved nearly all comments. Eric will check with Elika about the tests.
    2. Emilio will work on a concrete proposal for Define OffscreenCanvasRenderingContext2D.font setter in detail.
      1. No progress.
    3. Mason will comment on the Scoped Custom Element Registries issue.
      1. Justin commented, Ryosuke's concerns were addressed. Mason will draft a PR.
    4. Domenic will comment on the dialog element individual blockers with his opinion on how blocking/non-blocking they are toward further progress.
      1. Will wait for Domenic to comment on the remaining issues.
    5. Emilio will work on a PR and tests for Proposal: extend FocusOptions to allow specifying :focus-visible behavior.
      1. Done.
    6. Joey will add use counters to see potential breakage with adopting Chromium's behavior for Event bubbling on disabled form elements and decide which compat breakage is more tenable. Kagami will test more scenarios for event target.
      1. Use Counters were added, breakage seems high in prerelease channels, a quick fix is not an option. Plausible plans will be discussed in the GitHub issue.
    7. Mason will ensure the updated proposal is posted in the autocomplete attribute for street-address details issue.
      1. The new proposal is measurably better for the Brazil test case (4% -> 100%), positive feedback on the issue. Mason will update the group next time with even more test data. Looking almost ready for a spec PR, no objections raised.
    8. Domenic will open a new issue about alternative times for this meeting with several proposals to consider.
      1. Done.
  2. Carryovers from last time
  3. New topics
    1. [Emilio] focus delegate code seems wrongly only looking at children
      1. Will discuss next time with Emilio present.
    2. [Emilio] autofocus + delegateFocus handling doesn't make much sense to me
      1. Will discuss next time with Emilio present.
    3. [Tim] Which input types should readonly affect constraint validation for?
      1. The group agreed with Domenic's proposal in the issue.
    4. [Domenic] HTML Standard triage meeting times
      1. Agreement to try out the proposed changes, a question was raised about limiting the meeting to 30 minutes since it will be more frequent.

Action Items

  1. @meyerweb will check with Elika about the tests for the PR for directionality in the shadow DOM.
  2. @emilio will work on a concrete proposal for Define OffscreenCanvasRenderingContext2D.font setter in detail.
  3. @mfreed7 will draft a PR for Scoped Custom Element Registries.
  4. @domenic will comment on the dialog element individual blockers with his opinion on how blocking/non-blocking they are toward further progress.
  5. @mfreed7 will update the group next time with even more test data from the autocomplete attribute for street-address details issue.
  6. @past will update the calendar invite with the new agreed upon times.

@past past closed this as completed Aug 5, 2022
nt1m added a commit to nt1m/wpt that referenced this issue Aug 8, 2022
nt1m added a commit to web-platform-tests/wpt that referenced this issue Aug 9, 2022
moz-v2v-gh pushed a commit to mozilla/gecko-dev that referenced this issue Sep 5, 2022
…onstraint validation on 'unsupported' types, a=testonly

Automatic update from web-platform-tests
readonly attribute should still affect constraint validation on 'unsupported' types (#35389)

See whatwg/html#8133 and whatwg/html#8089
--

wpt-commits: b7eb2920ba4cea3af51fdc4e11eddacd26f9a3ac
wpt-pr: 35389
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

1 participant