Is there any chance for this to break web compatibility? Sounds like it shouldn't.
Regards, Florin. -----Original Message----- From: dev-platform [mailto:dev-platform-bounces+florin.mezei=softvisioninc...@lists.mozilla.org ] On Behalf Of Boris Zbarsky Sent: Monday, May 23, 2016 10:17 PM To: dev-platform@lists.mozilla.org Subject: Intent to implement and ship: spec changes to the .form property and "form" attribute on <label> elements Summary: The "form" content attribute on <label> elements no longer means anything. .form returns the .form of the labeled control, or null if nothing is labeled or the labeled thing has no .form. In particular, you can no longer associate a label with one form but associate its labeled control with a different form. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1268852 Spec: https://github.com/whatwg/html/pull/1120 and https://html.spec.whatwg.org/multipage/forms.html#the-label-element and https://html.spec.whatwg.org/multipage/forms.html#dom-label-form Estimated release: 49 devtools bug: none needed, I think. Support in other browsers: Chrome is planning to do this. See <https://groups.google.com/a/chromium.org/d/msg/blink-dev/QWyCpJjgfY8/TOxG9n -OAQAJ>. According to that message, Edge and WebKit don't support the "form" content attribute on <label> anyway; .form always returns the ancestor form in those engines. -Boris _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
