sitespeedio / sitespeedio/browsertime
LastVisualChange reports late values caused by invisible browser re-rasterization noise
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 652
- Forks
- 141
- Avg merge
- 3h 56m
- Merged PRs (30d)
- 5
Description
There's a problem that been there for years that we seen on Chrome testing Wikipedia where last visual change is reported late, even though there are no visible change. We can see that for example on:
https://github.com/user-attachments/assets/63f404ae-31eb-4a4b-8dd2-28f1bea9e005
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 tracing the LastVisualChange implementation and reproduce the late value on the linked Chrome Wikipedia recording. Investigate how invisible browser re-rasterization noise affects the measurement, then verify that the reported visual change matches visible changes without regressing existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100