Closed Bug 1937266 Opened 2 months ago Closed 2 months ago

[wpt-sync] Sync PR 49694 - [RasterInducingScroll] Force update even without raster invalidation

Categories

(Core :: Layout: Scrolling and Overflow, task, P4)

task

Tracking

()

RESOLVED FIXED
135 Branch
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

Component: web-platform-tests → Layout: Scrolling and Overflow
Product: Testing → Core

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

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ce4d589a4b7f [wpt PR 49694] - [RasterInducingScroll] Force update even without raster invalidation, a=testonly
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 135 Branch
You need to log in before you can comment on or make changes to this bug.