New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 8 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2017
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug

issue 536263

Show other hotlists

Hotlists containing this issue:

Sign in to add a comment

Issue 597642: select element with border-radius not scrolling when contents too long

Reported by, Mar 24 2016

Issue description

Chrome Version       : 49.0.2623.87 m
URLs (if applicable) :
Other browsers tested: IE11 OK, Edge OK
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
         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

Comment 1 by, Apr 1 2016

Components: Blink>Scroll
Labels: M-50 OS-Linux OS-Mac OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to repro this issue on Windows 7, MAC (10.11.3) & Ubuntu Trusty (14.04) for Google Chrome Stable Version - 49.0.2623.110

This is a Non-Regression issue existing from M30 - # 30.0.1549.0

Comment 2 by, Apr 7 2016

Components: Blink>Input>HitTesting
The hit test looks like it isn't testing the scrollbar in this case for some reason and is selecting the text underneath.

Comment 3 by, Apr 7 2016

Labels: Hotlist-Input-Dev
Status: Available (was: Untriaged)

Comment 4 by, May 17 2016

Blocking: 536263

Comment 5 by, 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.

Can you still reproduce?

Comment 6 by, Aug 9 2016

It's still happening for me.
I've recorded a screencast to show:

currently on windows 10

Comment 7 by, 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)

Comment 8 by, 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.

Comment 9 by, Aug 9 2016

That does not work for me. But, as long as you can reproduce it, cool.

Comment 10 by, Aug 25 2016

Components: -Blink>Input>HitTesting Blink>HitTesting
Moving Blink>Input>HitTesting to Blink>HitTesting

Comment 11 by, Aug 28 2017

Project Member
Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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 - Your friendly Sheriffbot

Comment 12 by, Aug 28 2017

Status: WontFix (was: Untriaged)
Seems to work fine on Win 10, Linux and high DPI Mac. Closing.

Sign in to add a comment