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

It's not clear how constraint validation works for FACE if the 'validation anchor' is null #10155

Open
EdgarChen opened this issue Feb 22, 2024 · 2 comments
Labels
topic: custom elements Relates to custom elements (as defined in DOM and HTML) topic: forms

Comments

@EdgarChen
Copy link
Member

What is the issue with the HTML Standard?

This is originated from https://bugzilla.mozilla.org/show_bug.cgi?id=1881199.

The validation anchor can be null as the anchor parameter of setValidity(flags, message, anchor) is optional, https://html.spec.whatwg.org/multipage/custom-elements.html#dom-elementinternals-setvalidity.

But https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#interactively-validate-the-constraints says

For elements that are form-associated custom elements, user agents should use their validation anchor instead, for the purposes of these actions.

It seems like Blink fallback to FACE itself when validation anchor is null. It looks reasonable to me, but I am not sure if this is something we would like to mention in the spec.

@jeripeierSBB
Copy link

There is also a bug report at webkit: https://bugs.webkit.org/show_bug.cgi?id=269832

@annevk annevk added topic: custom elements Relates to custom elements (as defined in DOM and HTML) topic: forms labels Feb 26, 2024
@annevk
Copy link
Member

annevk commented Feb 26, 2024

cc @whatwg/components

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: custom elements Relates to custom elements (as defined in DOM and HTML) topic: forms
Development

No branches or pull requests

3 participants