tabatkins / css-toggle

Proposal for a CSS Toggle spec

tabatkins/css-toggle Issues

"Disclosure pattern" should allow root+trigger on same (preceding sibling) element
Updated a year ago
do we actually want multiple `toggle-trigger` values?
Updated a year ago2
Allow toggles to work on elements with existing behavior
Updated a year ago8
allow connecting more distant elements to the same toggle
Updated a year ago20
Toggles for "slideshow"-style usage
Updated a year ago3
Nesting and toggle-trigger event propagation
Updated 2 years ago2
should the spec define how toggles behave when invoked on disabled elements
Updated 2 years ago2
how should selecting text interact with toggle-visibility?
Updated 2 years ago3
Do we need a one-directional (UA -> toggle state) variant of toggle-visibility?
Updated 2 years ago
Proposed ARIA heuristics
Updated 2 years ago13
[css-toggle-1] Implementation of different `toggling` patterns require different ARIA attributes
Updated 2 years ago2
should toggle-visibility have contain:paint or at least its z-ordering effects (stacking context) all of the time?
Updated 2 years ago7
definition of toggle scope should mention style containment
Updated 2 years ago3
should togglechange events fire in additional cases?
Updated 2 years ago1
states setter steps should also check length of list
Closed 2 years ago1
should empty list of toggle states be allowed?
Closed 2 years ago1
value matching should be described in terms of a toggle and a value
Closed 2 years ago1
should togglechange events fire when toggles don't actually change?
Closed 2 years ago1
CSSToggleEventInit should inherit from EventInit
Closed 2 years ago2
CSSToggleEvent constructor is wrong in IDL
Closed 2 years ago4
The 'toggle specifier' effects should be more automatic in the spec
Updated 2 years ago
"If t’s value is a list of idents" doesn't make sense
Closed 2 years ago3
<toggle-name> use of <custom-ident> should exclude 'none'
Closed 2 years ago
CSSToggle() constructor should throw exception in same cases that setStates throws exception
Closed 2 years ago
model document-wide implicit toggle groups as being on the root element
Updated 2 years ago1
how does repeating the same name for toggle-root and toggle-group work?
Updated 2 years ago1
clarify how toggles are supposed to be updated, and whether it should all happen in a single flush
Updated 2 years ago5
why are toggles an event target?
Closed 2 years ago1
Element.toggles should be readonly and [SameObject]
Closed 2 years ago1
spec should be more consistent with cycle versus overflow terminology
Updated 2 years ago
spec should be clear about how toggles interact with display:none and display:contents
Updated 2 years ago
toggle creation/replacement model is a bit unclear
Updated 2 years ago3
Persisting Toggles
Updated 2 years ago
Increment by a scroller's width when hooked to scroll snap
Updated 2 years ago1
alignment with state machines
Updated 2 years ago23
Allow creating toggle-roots without implicit toggling
Closed 2 years ago5
Allow for default toggle cycle list to not include all states
Updated 2 years ago
Should "activator" / activate be more integrated here?
Closed 2 years ago3
Toggle specifier error in spec
Closed 2 years ago1
Feedback on the tristate check example, and a suggestion
Closed 2 years ago6
bikeshed suggestion — `:checked` → `:toggled`
Closed 2 years ago1
Do we need a longhand for initial states?
Updated 2 years ago4
The spec should be clear on what happens if `toggle` is used on pseudo-elements
Updated 2 years ago1
Toggle groups are finicky, and should probably be a different feature entirely.
Updated 2 years ago5
Name conflict with toggle() from css-values-5
Updated 2 years ago
Is example 8 missing the toggle name?
Closed 3 years ago1
toggle names/possible values/numbers meaning
Updated 3 years ago1