Skip to content

Provide a fallback for validation anchor #11247

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.

Sign up for GitHub

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

Jump to bottom
Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Provide a fallback for validation anchor #11247

wants to merge 1 commit into from

Conversation

annevk
Copy link
Member

@annevk annevk commented Apr 22, 2025 •
edited by pr-preview bot
Loading

Fixes #10155.

  • At least two implementers are interested (and none opposed):
    • …
    • …
  • Tests are written and can be reviewed and commented upon at:
    • …
  • Implementation bugs are filed:
    • Chromium: …
    • Gecko: …
    • WebKit: …
    • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): …
    • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …
  • Corresponding HTML AAM & ARIA in HTML issues & PRs:
  • MDN issue is filed: …
  • The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)

/custom-elements.html ( diff )
@annevk annevk mentioned this pull request Apr 22, 2025
Open
@annevk
Copy link
Member Author

annevk commented Apr 22, 2025

(Although this is different from how it's implemented, I'm fairly certain it results in identical behavior. Implementations do the fallback during look up, but look up only happens when setValidity() has been called as otherwise the form-associated custom element would be considered valid.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant
@annevk