[w3ctag/design-reviews] Early design review: CSS Toggles (Issue #730)

Braw mornin' TAG!

I'm requesting a TAG review of CSS Toggles.

CSS toggles are a mechanism for associating toggleable state with a DOM element.  This state can be defined and connected to activations through CSS properties, and can be queried in CSS selectors.  This provides a declarative mechanism for specifying state that describes behaviors like the existing HTML behaviors for checkboxes or radio buttons.

  - Explainer¹ (minimally containing user needs and example code): https://css.oddbird.net/toggles/explainer/

  - Specification draft (early draft): https://tabatkins.github.io/css-toggle/

  - User research: none yet, but we hope to do some once we have a prototype
  - Security and Privacy self-review²: https://gist.github.com/dbaron/6dc75361b4dfad8333ad637b70d9be98

  - GitHub repo (if you prefer feedback filed there): https://github.com/tabatkins/css-toggle/

  - Primary contacts (and their relationship to the specification):
      - David Baron @dbaron, Google, implementor of prototype in Chromium
      - Miriam Suzanne @mirisuzanne, explainer author and author of demos and polyfill
      - Tab Atkins @tabatkins, Google, specification author
      - Nicole Sullivan @stubbornella, Google, project manager, advocate, and organizer of user studies
  - Organization/project driving the design: Google
  - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): [Chrome Status](https://chromestatus.com/feature/5072281125519360)

Further details:

  - [X] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - The group where the incubation/design work on this is being done: [Open UI](https://open-ui.org/) ([W3C info](https://www.w3.org/groups/cg/open-ui))
  - The group where standardization of this work is intended to be done: [CSS Working Group](https://wiki.csswg.org/) ([W3C info](https://www.w3.org/groups/wg/css)), at least assuming it continues to be a CSS feature
  - Existing major pieces of multi-stakeholder review or discussion of this design:
    - There's been some discussion of this in meetings of the Open UI CG.
  - Major unresolved issues with or opposition to this design:
    - There has been some discussion about to what extent this makes sense to be in CSS.  To some degree this breaks down into two separate questions:  (1) whether the intended uses are things that should be done in CSS and (2) whether it enables doing other things in CSS that should not be done in CSS.
  - This work is being funded by: Google

You should also know that...

This is *actually* an early-stage review.  The goal of what I'm doing in Chromium is to build an implementation that can be used to guide the design of this feature (by giving those involved an implementation to test), not to build something that we'd like to ship quickly.

Before we would consider shipping something in this space, we would (among other things) want to do further testing to validate that the result is more accessible than what people use today (or learn that we need to build in more distinctions that can be reflected into accessibility roles), and do additional development of the things that we hope can be built on top of toggles to validate that it works as a primitive.

We'd prefer the TAG provide feedback as:
  💬 leave review feedback as a **comment in this issue** and @-notify users listed above

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/730

You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/730@github.com>