Spec PR: whatwg/html#12424
Spec issue: whatwg/html#10293
WPT tests (tentative): web-platform-tests/wpt#59741
The HTML spec is adding a readonly content attribute to <fieldset>
that propagates a read-only state to descendant form controls
(parallel to the existing disabled attribute).
Pages to update once at least one engine ships:
Web/HTML/Element/fieldset — add readonly to the attributes table
alongside disabled, with a usage exampleWeb/API/HTMLFieldSetElement — add the readOnly IDL propertyWeb/API/HTMLElement#instance_methods (custom elements) — add
formReadonlyCallback to the form-associated custom element
lifecycle callbacks list, alongside formDisabledCallback- BCD entries for all of the above
Affected descendants are: <input> in states that support readonly
(text, search, url, tel, email, password, date, month, week, time,
datetime-local, number), <textarea>, and form-associated custom
elements. Descendants of the first <legend> child are exempt.
Filing now so it's tracked; no action needed until shipping.
Spec PR: whatwg/html#12424
Spec issue: whatwg/html#10293
WPT tests (tentative): web-platform-tests/wpt#59741
The HTML spec is adding a
readonlycontent attribute to<fieldset>that propagates a read-only state to descendant form controls
(parallel to the existing
disabledattribute).Pages to update once at least one engine ships:
Web/HTML/Element/fieldset— addreadonlyto the attributes tablealongside
disabled, with a usage exampleWeb/API/HTMLFieldSetElement— add thereadOnlyIDL propertyWeb/API/HTMLElement#instance_methods(custom elements) — addformReadonlyCallbackto the form-associated custom elementlifecycle callbacks list, alongside
formDisabledCallbackAffected descendants are:
<input>in states that support readonly(text, search, url, tel, email, password, date, month, week, time,
datetime-local, number),
<textarea>, and form-associated customelements. Descendants of the first
<legend>child are exempt.Filing now so it's tracked; no action needed until shipping.