Standardize which scroll state ought to be restored during page restoration.
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 3.2k
- PR merge metrics
- PR metrics pending
Description
As per the discussion in bz1593064, there are presently interop issues with which page scroll state is being restored when users press back/forward (etc). For instance, pages which call window.scroll(0,0) may be ignored on Chrome, but not on Firefox, leading to users reporting webcompat issues such as this one with ABC News. To prevent this kind of issue, it seems worth aligning on which scroll state ought to be restored and when.
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 by reading the linked bz1593064 discussion and the ABC News webcompat example to understand the competing scroll-restoration behaviors. Done means reaching a clear agreement on which scroll state should be restored and when, suitable for standardizing in the HTML specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100