[css-toggles] Clarify what "persistent state" means
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
In https://tabatkins.github.io/css-toggle/#toggles (and elsewhere), the notion of "persistent state" is used:
Toggles are persistent state on an element, and are not directly affected by any CSS properties.
It may be useful to define this, or clarify in a security and privacy considerations section that toggles aren't cookies, or storage. Or to define what persistent state means so it's more obvious.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the linked CSS Toggles specification, read the persistent state wording in the Toggles section, and search the draft for other occurrences. Clarify what the term means, including whether toggles are distinct from cookies or storage, and ensure the explanation is consistent wherever the term appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100