[Webkit-unassigned] [Bug 223729] New: REGRESSION(r 274381) [WPE] css3/scroll-snap/scroll-snap-wheel-event.html is flaky failing in release mode

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=223729

            Bug ID: 223729
           Summary: REGRESSION(r 274381) [WPE]
                    css3/scroll-snap/scroll-snap-wheel-event.html is flaky
                    failing in release mode
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: UI Events
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: lmoura at igalia.com

css3/scroll-snap/scroll-snap-wheel-event.html

Usually the first assertion fails, but occasionally the second one fails too. Modifying the test to print the actual values:

-PASS horizontalContainer.scrollLeft is 200
-PASS verticalContainer.scrollTop is 185
+FAIL horizontalContainer.scrollLeft should be 200. Was 0.
+FAIL verticalContainer.scrollTop should be 185. Was 200.
 PASS successfullyParsed is true
+Some tests failed.

Checking the event dispatcher, the debug build ScrollingTree::determineWheelEventProcessing always returns in the isSynchronousDispatchRegion (~95) check when determining the processing steps for both events, thus handling the event in the main thread.

Meanwhile, in the Release build, most of the time, during the handling of the first event, the ScrollingTree's m_treeState.eventTrackingRegions is empty and the method returns only ScrollingThread in the processing steps. Rarely it has the same behavior as the debug build.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210325/f4d49cad/attachment.htm>