-
Notifications
You must be signed in to change notification settings - Fork 1
Issues: tabatkins/css-toggle
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
"Disclosure pattern" should allow root+trigger on same (preceding sibling) element
#49
opened Mar 9, 2023 by
tabatkins
Do we need a one-directional (UA -> toggle state) variant of toggle-visibility?
#45
opened Nov 9, 2022 by
dbaron
should the spec define how toggles behave when invoked on disabled elements
#44
opened Oct 27, 2022 by
stubbornella
[css-toggle-1] Implementation of different
toggling
patterns require different ARIA attributes
#40
opened Sep 16, 2022 by
FremyCompany
The 'toggle specifier' effects should be more automatic in the spec
#33
opened Aug 25, 2022 by
tabatkins
spec should be more consistent with cycle versus overflow terminology
#31
opened Aug 25, 2022 by
dbaron
clarify how toggles are supposed to be updated, and whether it should all happen in a single flush
#27
opened Aug 16, 2022 by
dbaron
how does repeating the same name for toggle-root and toggle-group work?
#25
opened Jul 19, 2022 by
dbaron
spec should be clear about how toggles interact with display:none and display:contents
#24
opened Jul 15, 2022 by
dbaron
model document-wide implicit toggle groups as being on the root element
#23
opened Jul 14, 2022 by
dbaron
The spec should be clear on what happens if
toggle
is used on pseudo-elements
#11
opened Jan 26, 2022 by
FremyCompany
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.