Iframe with overflow-y:scroll adds an unusable scroll bar on retina display |
|||||||||
Issue description
Version: 50.0.2661.102
OS: OSX 10.11.4
What steps will reproduce the problem?
1) Under general preferences on OSX, set "show scroll bars" to "Automatically based on mouse or trackpad" or "Always"
2) With Chrome on a non-retina display, load main.html below containing a single iframe with overflow-y set to 'scroll'. The iframe content is slightly bigger than the iframe itself, causing overflow and generating a working scrollbar.
3) Move the Chrome window to the Apple macbook pro retina display
What is the expected output?
The rendering between displays is consistent. The scrollbars stay the same.
This issue is not reproducible in other browsers such as Safari and Firefox.
What do you see instead?
A disabled, unusable scrollbar is rendered over the existing iframe scrollbar (screencap gif attached)
Please use labels and text to provide additional information.
====== main.html ======
<html>
<head>
<style type="text/css">
iframe {
overflow-y: scroll;
width: 550px;
height: 450px;
}
</style>
</head>
<body>
<iframe src="tooBigForIframe.html"/>
</body>
</html>
====== tooBigForIframe.html ======
<html>
<head>
<style type="text/css">
div {
height: 600px; /* This dimension is slightly larger than the parent iframe */
width: 500px;
border: 2px solid blue;
}
</style>
</head>
<body>
<div></div>
</body>
</html>
,
May 13 2016
,
May 19 2016
This may be an artifact of switching the scrollbars to being composited when switching to a retina display. +ccameron@ are you able to take a look and verify?
,
May 19 2016
,
May 31 2016
I am not able to work on Mac input/scrolling bugs. Routing to shrike for the moment -- this is an area that doesn't have an owner.. Please try to reproduce on a Pixel, to see if this is Mac specific. Also, have you tried a bisect? Is this a regression?
,
Jun 1 2016
,
Jun 2 2016
,
Jun 2 2016
[There is not confidential information in this ticket so making it public]
,
Jun 2 2016
I can reproduce this on ChromeOS too in current Stable (M50) but not in dev channel (M52). Here is the repro in #1: http://jsbin.com/kehehadeke. So it has been fixed already. I don't have a M51 device handy to test to make sure it is in M51 or no but I suspect this is the same issue as http://crbug.com/383855 which was fixed in M51 by jbroman@. If this is true the we should mark as duplicate and close.
,
Jun 2 2016
Assuming you mean bug 384154 , this sounds the same as that (fix in M51, as majidvp@ says).
,
Jun 2 2016
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by ejochman@google.com
, May 13 2016