Should it be possible to light dismiss overscroll areas?
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
It's been suggested that some use cases for overscroll actions might want the overscroll area to be light-dismissable. It seems roughly straightforward to bring in popover's definition of light dismiss, so that clicking outside both the invoker button and the overscroll area itself constitutes a light dismiss signal, which closes the overscroll area. Also, hitting ESC should light dismiss.
So first question: is this needed/desired for some concrete use cases? It'd be good to enumerate those.
Second question: should this be optional behavior? Or should all overscroll areas light dismiss? If this is optional behavior, what should the mechanism be for authors to opt in or out? One (perhaps bad) idea would be to add values to the overscrollcontainer attribute, such as overscrollcontainer="lightdismiss".
Thoughts?
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
Read the overscroll actions explainer and the linked discussion in issue 1372 first. Enumerate concrete use cases, then resolve whether light dismissal should be universal or optional and how authors would opt in or out. Done means the issue has a documented consensus on the behavior and mechanism.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100