Bug 260639

Summary: [wpt.fyi] Dropdown menu not scrollable in products view
Product: WebKit Reporter: Abrar Rahman Protyasha <a_protyasha>
Component: ScrollingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: a_protyasha, simon.fraser, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Reproduction on Safari, cannot scroll.
none
Can scroll on Chrome. none

Abrar Rahman Protyasha
Reported 2023-08-23 17:26:27 PDT
Created attachment 467404 [details] Reproduction on Safari, cannot scroll. Dropdown menus in the Products view of the web-platform-tests dashboard website cannot be scrolled on Safari. The same menus can be scrolled on Firefox and Chrome. Please refer to the attached screen recording for a reproduction.
Attachments
Reproduction on Safari, cannot scroll. (4.50 MB, video/quicktime)
2023-08-23 17:26 PDT, Abrar Rahman Protyasha
no flags
Can scroll on Chrome. (2.99 MB, video/quicktime)
2023-08-23 17:26 PDT, Abrar Rahman Protyasha
no flags
Radar WebKit Bug Importer
Comment 1 2023-08-23 17:26:39 PDT
Abrar Rahman Protyasha
Comment 2 2023-08-23 17:26:46 PDT
Created attachment 467405 [details] Can scroll on Chrome.
Abrar Rahman Protyasha
Comment 3 2023-08-23 17:27:21 PDT
The dropdown menu has a CSS attribute `--paper-input-container-input_-_overflow: hidden` which seems a little suspect, but my interpretation says we _shouldn't_ be scrolling on this menu in that case.
Abrar Rahman Protyasha
Comment 4 2023-08-23 17:37:12 PDT
Repro steps: 1. Navigate to https://wpt.fyi/results/pointerevents/pointerevent_movementxy.html%3Fmouse?label=master&label=experimental&product=chrome&product=firefox&product=safari&product=webkitgtk&view=interop&q=label%3Ainterop-2023-events 2. Click on "Edit" to the far-right on the blue info bar. 3. In the Products pane, expand any of the "Browser" dropdown menus
Simon Fraser (smfr)
Comment 5 2025-06-03 16:21:26 PDT
I can't reproduce now. Looks like this was fixed.
Note You need to log in before you can comment on or make changes to this bug.