Intent to Implement and Ship: Drop LABEL element from form-associated elements

[TAMURA, Kent]

Contact emails tk...@chromium.org Spec https://html.spec.whatwg.org/multipage/forms.html#form-associated-element

Summary The HTML specification was changed so that LABEL element isn't a form-associated element. There are two behavior changes: - Remove `form' content attribute support from LABEL element - Change the behavior of `form' IDL attribute of LABEL element so that it returns the form owner of the associated control.

Motivation

Before this change, it's possible that a LABEL element is associated to form A, and its associated form control is associated to another form B. It's confusing.

Interoperability risk Firefox: No public signals Edge: Mixed public signals Safari: Mixed public signals Web developers: No signals

WebKit and Edge don't support `form' content attribute of LABEL element. So interoperability risk should be low.

Compatibility risk

Low.  We have data.

`form' content attribute of LABEL element is used in less than 0.0023% of page views.
https://www.chromestatus.com/metrics/feature/timeline/popularity/986

label.form is different from label.control.form in less than 0.0016% of page views.
https://www.chromestatus.com/metrics/feature/timeline/popularity/1261

Ongoing technical constraints N/A

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes or no. Yes

Tracking bug http://crbug.com/607868

Link to entry on the Chrome Platform Status https://www.chromestatus.com/features/5661555072958464

Requesting approval to ship?

Yes

--

TAMURA Kent
Software Engineer, Google

[Chris Harrelson]

LGTM1

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

[Dimitri Glazkov]

LGTM2

[Rick Byers]

LGTM3