css-toggle
css-toggle copied to clipboard
tabatkins
Proposal for a CSS Toggle spec
Whether the "summary" is inside the "details" or before it shouldn't really make a difference, and some of the oddbird examples show off exactly that markup pattern. Right now it's...
Currently the `toggle-trigger` property takes a list of toggles to trigger. I haven't seen any demos so far that involve using multiple `toggle-trigger` values. I also think multiple `toggle-trigger` values...
The current [toggle-trigger production](https://tabatkins.github.io/css-toggle/#typedef-toggle-trigger) says: > If the element already has existing activation behavior from the host language, this value does nothing. I'm not sure how clearly defined the term...
There are use cases for connecting more distant elements with the same toggle. For example, typical tab component markup might look something like (in very abbreviated form, with names I...
Toggles seem reasonable fit to represent slideshows as well - each slide has a toggle, with a group on the root ensuring that only one is displayed at a time,...
Providing opportunity for any HTML element node to (technically) become active control element, this creates possibility to produce nested active structures. Such structures were not technically possible (e.g. nested buttons,...
The [spec for `toggle-visibility`](https://tabatkins.github.io/css-toggle/#toggle-visibility-property) currently says that it works the same way as `content-visibility: auto` except that it's tied to the state of a toggle instead of to being onscren....
I think it's possible that it would be good to have a one-directional variant of `toggle-visibility`. Currently `toggle-visibility` does two things: 1. It hides/shows the element based on the state...
Aaron and I have been working on the ARIA auto-detection heuristics, and I think I've got them accurately distilled down to this if/then chain: * If 'toggle-root' is on a...