resize event needs to deferred until after page visibility becomes visible
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 3.2k
- PR merge metrics
- PR metrics pending
Description
What is the issue with the HTML Standard?
See https://github.com/WebKit/WebKit/pull/46590. We encountered a web compatibility issue on Google spreadsheet where dispatching resize event before visibilitychange event results in a bad rendering. The specification currently says to "run the resize steps" without regards to whether the page is currently visible or not but this behavior is not Web compatible. Web apps such as Google spreadsheet expects to receive resize event only after visibilitychange event had been fired to make the page visible first.
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 with the HTML Standard issue's links to the CSSOM View “run the resize steps” definition and WebKit pull request 46590, then trace how resize and visibilitychange are ordered for hidden pages. Done means the specification clearly defines resize delivery after the page becomes visible, matching the compatibility behavior described for Google Sheets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100