[wpt-sync] Sync PR 49694 - [RasterInducingScroll] Force update even without raster invalidation
Categories
(Core :: Layout: Scrolling and Overflow, task, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox135 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 49694 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/49694
Details from upstream follow.
Xianzhu Wang <wangxianzhu@chromium.org> wrote:
[RasterInducingScroll] Force update even without raster invalidation
The following changes won't cause raster invalidation:
- A scroller is added/removed without any visible change;
- Some scrolling content out of a non-composited scroller's
scrollport changes.Previously we skipped cc layer update because nothing visible
changed. However, future raster-inducing scroll without
main-thread update could scroll the out-of-date content into
view.Now force update in RasterInducingScroll in
ContentLayerClientImpl::UpdateCcLayer().Bug: 364669904
Change-Id: I636d3f92a2a98db50f30160c2e214735311d6769
Reviewed-on: https://chromium-review.googlesource.com/6090759
WPT-Export-Revision: 277517ae712e3ba0dbeff3b3b13896f316cefad7
Assignee | ||
Updated•2 months ago
|
Assignee | ||
Comment 1•2 months ago
|
||
Assignee | ||
Comment 2•2 months ago
|
||
Assignee | ||
Comment 3•2 months ago
|
||
CI Results
Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 2 tests
Status Summary
Firefox
PASS
: 2
Chrome
FAIL
: 2
Safari
PASS
: 2
Links
Comment 5•2 months ago
|
||
bugherder |
Description
•