[css-scroll-snap] unintuitive/inconsistent behavior due to snap-overflow definition
Open
Nobody has claimed this yet.
css-scroll-snap-1
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
Steps to reproduce to see the behavior
- Open https://bugzilla.mozilla.org/attachment.cgi?id=9275658
- Try to scroll down by using arrow down key until the scroll position snaps to the top edge of "4" element
- During the scrolling down phase, you can see several snapped points on "3" element due to the snap-overflow
3.1 Note that there's a bug on Firefox that there's no snap points other than the top edge on the "3" element - Try to scroll up by using arrow up key
Then it snaps to the top edge of the 3 element.
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
Open the linked reproduction and read the CSS Scroll Snap Level 1 snap-overflow definition. Reproduce the downward and upward arrow-key scrolling behavior, then compare it with the Firefox issue linked in the report. Done means the expected snapping behavior or required specification change is agreed and recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100