Thank you Thomas for sharing! We’ll reference your polyfill as we get closer to shipping. On Tuesday, August 4, 2026 at 10:18:32 AM UTC-7 Thomas Steiner wrote:
> Great news! For the required developer signals once this gets closer to > shipping, feel free to reference my polyfill > <https://github.com/tomayac/input-switch-polyfill>. > > On Monday, July 20, 2026 at 10:58:56 PM UTC+2 Leo Lee wrote: > >> *Contact emails* >> [email protected], [email protected], [email protected] >> >> *Explainer* >> https://open-ui.org/components/switch.attribute.explainer >> >> *Specification* >> https://github.com/whatwg/html/pull/9546 >> >> *Summary* >> This proposal adds a switch attribute to <input type="checkbox"> for >> binary on/off settings. The control reuses the checkbox's checked state, >> form participation, and label association while exposing it as a switch to >> assistive technologies. It provides a platform-native appearance and >> supports familiar click, keyboard, and touch interactions. Authors can >> customize the track and thumb using proposed CSS pseudo-elements, with >> animation supplied by the user agent. The attribute targets common switch >> use cases. Cases requiring child content are not supported by the >> attribute, and a standalone <switch> element is out of scope for this >> proposal. >> >> *Blink component* >> Blink>Forms >> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EForms%22> >> >> *Web Feature ID* >> switch-control <https://webstatus.dev/features/switch-control> >> >> *Motivation* >> Switches are common in settings, preferences, feature controls, and >> consent interfaces, but the HTML Standard does not currently define a >> native switch control. Developers instead rely on JavaScript component >> libraries, visually hidden checkboxes with custom CSS, or generic elements >> with role="switch". Depending on the approach, developers may need to >> recreate accessibility semantics, keyboard handling, state management, or >> form participation. These approaches can result in inconsistent behavior >> and accessibility, fragile implementations, and unnecessary JavaScript >> costs. >> >> *Initial public proposal* >> https://github.com/whatwg/html/issues/4180 >> >> *Requires code in //chrome?* >> False >> >> *Tracking bug* >> https://issues.chromium.org/issues/41484737 >> >> *Estimated milestones* >> No milestones specified >> >> *Link to entry on the Chrome Platform Status* >> https://chromestatus.com/feature/5178587742339072?gate=5133019548614656 >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com/>. >> >> -- 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/21a045a3-f050-4120-86bd-cb9cad86ced1n%40chromium.org.
