Bug 258543

Summary: [WPE] scrollingcoordinator/scrolling-tree test failures
Product: WebKit Reporter: Diego Pino <dpino>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: bugs-noreply, zdobersek
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

Diego Pino
Reported 2023-06-26 19:56:30 PDT
The following scrollingcoordinator/scrolling-tree tests are failing: scrollingcoordinator/scrolling-tree/composited-in-offscreen-fixed.html scrollingcoordinator/scrolling-tree/fixed-inside-relative-inside-stacking-overflow-inside-transformed.html scrollingcoordinator/scrolling-tree/fixed-inside-stacking-overflow-inside-transformed.html scrollingcoordinator/scrolling-tree/fixed-position-within-transformed.html I don't whether it would make sense to emit new baselines specific for WPE. https://build.webkit.org/results/WPE-Linux-64-bit-Release-Tests/265533%40main%20%2810853%29/scrollingcoordinator/scrolling-tree/composited-in-offscreen-fixed-diff.txt --- /home/buildbot/worker/WPE-Linux-64-bit-Release-Tests/build/layout-test-results/scrollingcoordinator/scrolling-tree/composited-in-offscreen-fixed-expected.txt +++ /home/buildbot/worker/WPE-Linux-64-bit-Release-Tests/build/layout-test-results/scrollingcoordinator/scrolling-tree/composited-in-offscreen-fixed-actual.txt @@ -4,8 +4,8 @@ (scrollable area size 800 600) (contents size 800 600) (scrollable area parameters - (horizontal scroll elasticity 2) - (vertical scroll elasticity 2) + (horizontal scroll elasticity 1) + (vertical scroll elasticity 1) (horizontal scrollbar mode 0) (vertical scrollbar mode 0)) (layout viewport at (0,0) size 800x600) https://build.webkit.org/results/WPE-Linux-64-bit-Release-Tests/265533%40main%20%2810853%29/scrollingcoordinator/scrolling-tree/fixed-inside-relative-inside-stacking-overflow-inside-transformed-diff.txt --- /home/buildbot/worker/WPE-Linux-64-bit-Release-Tests/build/layout-test-results/scrollingcoordinator/scrolling-tree/fixed-inside-relative-inside-stacking-overflow-inside-transformed-expected.txt +++ /home/buildbot/worker/WPE-Linux-64-bit-Release-Tests/build/layout-test-results/scrollingcoordinator/scrolling-tree/fixed-inside-relative-inside-stacking-overflow-inside-transformed-actual.txt @@ -4,8 +4,8 @@ (scrollable area size 785 600) (contents size 785 5021) (scrollable area parameters - (horizontal scroll elasticity 2) - (vertical scroll elasticity 2) + (horizontal scroll elasticity 1) + (vertical scroll elasticity 1) (horizontal scrollbar mode 0) (vertical scrollbar mode 0) (allows vertical scrolling 1)) @@ -21,8 +21,8 @@ (requested scroll position 0 50) (requested scroll position represents programmatic scroll 1) (scrollable area parameters - (horizontal scroll elasticity 0) - (vertical scroll elasticity 0) + (horizontal scroll elasticity 1) + (vertical scroll elasticity 1) (horizontal scrollbar mode 0) (vertical scrollbar mode 0) (allows vertical scrolling 1))
Attachments
Diego Pino
Comment 1 2025-06-20 06:54:49 PDT
Tests 'scrollingcoordinator/scrolling-tree/fixed-inside-stacking-overflow-inside-transformed.html' has been passing consistently since long time ago (>4000 revisions): - https://results.webkit.org/?platform=WPE&&suite=layout-tests&test=scrollingcoordinator/scrolling-tree/fixed-inside-stacking-overflow-inside-transformed.html&limit=4000 As for the other tests, their baseline was updated in 296369@main and the tests are green now: - https://results.webkit.org/?platform=WPE&&suite=layout-tests&test=scrollingcoordinator/scrolling-tree/composited-in-offscreen-fixed.html&suite=layout-tests&test=scrollingcoordinator/scrolling-tree/fixed-inside-relative-inside-stacking-overflow-inside-transformed.html&suite=layout-tests&test=scrollingcoordinator/scrolling-tree/fixed-position-within-transformed.html&limit=4000 Platform ios also emits own baselines for these tests. Even if the GLIB baseline is not correct, having a platform baseline will help detect when a change affecting these tests is introduced. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.