-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scroll offsets are sometimes lost when updating WebRender display list #31807
Labels
Comments
delan
added
C-untriaged
New issues that haven't been triaged yet
A-gfx/compositing
labels
Mar 21, 2024
|
5 tasks
4 tasks
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
Mar 27, 2024
…r display lists WebRender does not preserve spatial tree offsets when updating the spatial tree. Updating the spatial tree of a pipeline can also update the spatial tree of child pipelines. This change ensures that WebRender always gets the scroll offsets of the entire scene when modifying display lists in a way that may rebuild the spatial tree. Fixes servo#31807.
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
Mar 29, 2024
…r display lists WebRender does not preserve spatial tree offsets when updating the spatial tree. Updating the spatial tree of a pipeline can also update the spatial tree of child pipelines. This change ensures that WebRender always gets the scroll offsets of the entire scene when modifying display lists in a way that may rebuild the spatial tree. Fixes servo#31807.
github-merge-queue bot
pushed a commit
that referenced
this issue
Apr 3, 2024
…r display lists (#31892) WebRender does not preserve spatial tree offsets when updating the spatial tree. Updating the spatial tree of a pipeline can also update the spatial tree of child pipelines. This change ensures that WebRender always gets the scroll offsets of the entire scene when modifying display lists in a way that may rebuild the spatial tree. Fixes #31807.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To reproduce:
The text was updated successfully, but these errors were encountered: