select element with border-radius not scrolling when contents too long
Reported by
tfranc...@gmail.com,
Mar 24 2016
|
|||||||
Issue descriptionChrome Version : 49.0.2623.87 m URLs (if applicable) : https://jsfiddle.net/69y1f8vL/3/ Other browsers tested: IE11 OK, Edge OK Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: Firefox: IE: OK What steps will reproduce the problem? (1) create <select> element with border-radius set (4px is what i used) (2) have contents longer than available area (<select> width: 100px) (3) attempt to use scroll bar over where long text lies What is the expected result? no scrolling happens, or control of scrollbar allowed What happens instead? text underneath is selected Please provide any additional information below. Attach a screenshot if possible.
,
Apr 7 2016
The hit test looks like it isn't testing the scrollbar in this case for some reason and is selecting the text underneath.
,
Apr 7 2016
,
May 17 2016
,
Aug 9 2016
I cannot reproduce this, actually, on Windows 7. I also forked your fiddle to create one with two select boxes (one with a radius and one without) and I cannot reproduce any difference between them. https://jsfiddle.net/s53vuhaL/ Can you still reproduce?
,
Aug 9 2016
It's still happening for me. I've recorded a screencast to show: https://drive.google.com/open?id=0B5147BfWGcIZZWpScmdvQk85cEk currently on windows 10
,
Aug 9 2016
So weird... I wonder, what does about:gpu say in the first section? Mine - Canvas: Hardware accelerated Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Native GpuMemoryBuffers: Software only. Hardware acceleration disabled Rasterization: Software only. Hardware acceleration disabled Video Decode: Hardware accelerated Video Encode: Hardware accelerated WebGL: Hardware accelerated And what does about:version say in the Command Line field after the executable? Mine says - --flag-switches-begin --enable-devtools-experiments --enable-quic --flag-switches-end (But those are surely unrelated)
,
Aug 9 2016
it's likely a hdpi compositor hit testing issue. phistuck@ the key to trying to replicate it is setting your device scale in devtools and simulating a hpdi device if you don't natively have one.
,
Aug 9 2016
That does not work for me. But, as long as you can reproduce it, cool.
,
Aug 25 2016
Moving Blink>Input>HitTesting to Blink>HitTesting
,
Aug 28 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 28 2017
Seems to work fine on Win 10, Linux and high DPI Mac. Closing. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by rnimmagadda@chromium.org
, Apr 1 2016Components: Blink>Scroll
Labels: M-50 OS-Linux OS-Mac OS-Windows
Status: Untriaged (was: Unconfirmed)