tabatkins css-toggle issues

tabatkins / css-toggle

Proposal for a CSS Toggle spec

Creative Commons Zero v1.0 Universal

28 stars 1 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

"Disclosure pattern" should allow root+trigger on same (preceding sibling) element

#49 tabatkins opened 1 year ago
0
do we actually want multiple `toggle-trigger` values?

#48 dbaron opened 1 year ago
2
Toggles for "slideshow"-style usage

#47 tabatkins opened 1 year ago
3
allow connecting more distant elements to the same toggle

#46 dbaron opened 1 year ago
20
Do we need a one-directional (UA -> toggle state) variant of toggle-visibility?

#45 dbaron opened 1 year ago
0
should the spec define how toggles behave when invoked on disabled elements

#44 stubbornella opened 1 year ago
2
Nesting and toggle-trigger event propagation

#43 myfonj opened 1 year ago
2
how should selecting text interact with toggle-visibility?

#42 dbaron opened 2 years ago
3
Proposed ARIA heuristics

#41 tabatkins opened 2 years ago
13
[css-toggle-1] Implementation of different `toggling` patterns require different ARIA attributes

#40 FremyCompany opened 2 years ago
2
Allow toggles to work on elements with existing behavior

#39 mirisuzanne opened 2 years ago
8
should toggle-visibility have contain:paint or at least its z-ordering effects (stacking context) all of the time?

#38 dbaron opened 2 years ago
7
states setter steps should also check length of list

#37 dbaron closed 2 years ago
1
should togglechange events fire in additional cases?

#36 dbaron opened 2 years ago
1
should togglechange events fire when toggles don't actually change?

#35 dbaron closed 2 years ago
1
CSSToggleEventInit should inherit from EventInit

#34 dbaron closed 2 years ago
2
The 'toggle specifier' effects should be more automatic in the spec

#33 tabatkins opened 2 years ago
0
why are toggles an event target?

#32 dbaron closed 2 years ago
1
spec should be more consistent with cycle versus overflow terminology

#31 dbaron opened 2 years ago
0
CSSToggle() constructor should throw exception in same cases that setStates throws exception

#30 dbaron closed 2 years ago
0
CSSToggleEvent constructor is wrong in IDL

#29 dbaron closed 2 years ago
4
definition of toggle scope should mention style containment

#28 dbaron opened 2 years ago
3
clarify how toggles are supposed to be updated, and whether it should all happen in a single flush

#27 dbaron opened 2 years ago
5
Element.toggles should be readonly and [SameObject]

#26 dbaron closed 2 years ago
1
how does repeating the same name for toggle-root and toggle-group work?

#25 dbaron opened 2 years ago
1
spec should be clear about how toggles interact with display:none and display:contents

#24 dbaron opened 2 years ago
0
model document-wide implicit toggle groups as being on the root element

#23 dbaron opened 2 years ago
1
value matching should be described in terms of a toggle and a value

#22 dbaron closed 2 years ago
1
"If t’s value is a list of idents" doesn't make sense

#21 dbaron closed 2 years ago
3
toggle creation/replacement model is a bit unclear

#20 dbaron opened 2 years ago
3
should empty list of toggle states be allowed?

#19 dbaron closed 2 years ago
1
Support syntax for named states

#18 mirisuzanne closed 2 years ago
0
Persisting Toggles

#17 bramus opened 2 years ago
0
Fix typo

#16 bramus closed 2 years ago
0
Increment by a scroller's width when hooked to scroll snap

#15 tabatkins opened 2 years ago
1
<toggle-name> use of <custom-ident> should exclude 'none'

#14 dbaron closed 2 years ago
0
Allow creating toggle-roots without implicit toggling

#13 flackr closed 2 years ago
5
Allow for default toggle cycle list to not include all states

#12 flackr opened 2 years ago
0
The spec should be clear on what happens if `toggle` is used on pseudo-elements

#11 FremyCompany opened 2 years ago
1
Toggle groups are finicky, and should probably be a different feature entirely.

#10 FremyCompany opened 2 years ago
5
Name conflict with toggle() from css-values-5

#9 Loirooriol opened 2 years ago
0
Toggle specifier error in spec

#8 bkardell closed 2 years ago
1
alignment with state machines

#7 argyleink opened 3 years ago
23
Feedback on the tristate check example, and a suggestion

#6 jonathantneal closed 2 years ago
6
bikeshed suggestion — `:checked` → `:toggled`

#5 jonathantneal closed 2 years ago
1
toggle names/possible values/numbers meaning

#4 bkardell opened 3 years ago
1
Is example 8 missing the toggle name?

#3 bkardell closed 3 years ago
1
Should "activator" / activate be more integrated here?

#2 bkardell closed 2 years ago
3
Do we need a longhand for initial states?

#1 mirisuzanne opened 3 years ago
4