Bug 234618

Summary: REGRESSION (r287364): Three scrolling API tests consistently failing
Product: WebKit Reporter: Ryan Haddad <ryanhaddad>
Component: WebKit Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: simon.fraser, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

Description Ryan Haddad 2021-12-22 14:27:14 PST
The following API tests are failing on macOS bots after r287364:

    TestWebKitAPI.WebKit.FirstResponderScrollingPosition
        LEAK: 1 WebProcessPool
        LEAK: 2 WebPageProxy
        
        /Volumes/Data/worker/monterey-debug/build/Tools/TestWebKitAPI/Tests/mac/FirstResponderScrollingPosition.mm:83
        JS expression: window.scrollY
               Actual: 0
             Expected: 40
        
    TestWebKitAPI.WebKit.ScrollByLineCommands
        LEAK: 1 WebProcessPool
        
        /Volumes/Data/worker/monterey-debug/build/Tools/TestWebKitAPI/Tests/WebKit/mac/EditorCommands.mm:73
        JS expression: window.scrollY
               Actual: 0
             Expected: 40
        
        
        /Volumes/Data/worker/monterey-debug/build/Tools/TestWebKitAPI/Tests/WebKit/mac/EditorCommands.mm:78
        JS expression: window.scrollY
               Actual: 22
             Expected: 0
        
    TestWebKitAPI.WebKit.SpacebarScrolling
        LEAK: 1 WebProcessPool
        
        /Volumes/Data/worker/monterey-debug/build/Tools/TestWebKitAPI/Tests/WebKit/SpacebarScrolling.cpp:104
        JS expression: isDocumentScrolled()
               Actual: false
             Expected: true



https://results.webkit.org/?suite=api-tests&suite=api-tests&suite=api-tests&test=TestWebKitAPI.WebKit.SpacebarScrolling&test=TestWebKitAPI.WebKit.FirstResponderScrollingPosition&test=TestWebKitAPI.WebKit.ScrollByLineCommands
Comment 1 Radar WebKit Bug Importer 2021-12-22 14:27:27 PST
<rdar://problem/86826065>
Comment 2 Simon Fraser (smfr) 2021-12-22 14:32:10 PST
Fixing via bug 234620.

*** This bug has been marked as a duplicate of bug 234620 ***