-
Notifications
You must be signed in to change notification settings - Fork 23
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
Form-associated custom elements #47
Comments
This is under development. |
I believe I found a bug in both chrome and firefox' implementations, namely that a FACE in a fieldset should have it's UPDATE: Mozilla and Chrome both closed as WONTFIX, but I believe this is still a problem, so I filed a spec bug |
Does anyone happen to know who originally proposed form-associate custom elements (so I can give due credit with a |
(Added in whatwg/html#4383 by tkent from Google referencing WICG/webcomponents#187 by Hayato Ito (also Google) which was a continuation of https://www.w3.org/Bugs/Public/show_bug.cgi?id=24603 filed by Erik Arvidsson in 2014 (strongly suspect still at Google back then).) |
Closing as we've identified our position. |
Request for position on form-associated custom elements
Information about the spec
Design reviews and vendor positions
Bugs tracking this feature
Anything else we need to know
APIs using for allowing custom elements to participate in form submission and constraint validation. Chromium and Mozilla have shipped this feature and WebKit has begun implementing
ElementInternals
; however, WebKit's implementation currently lacks the form-associated APIs.The text was updated successfully, but these errors were encountered: