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

Issue 789262 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Border Radius misbehaves on low dpi display

Reported by mivan...@gmail.com, Nov 28 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
1. Visit codepen: https://codepen.io/shmargum/pen/xPygvw
2. Make sure you are on a low-dpi screen
3. Hover over each of the 5 elements
4. Bugs should be visible on elements 2, 3, 4, and 5 (not 1)
5. This bug exists on elements with an odd width/height (not even).

What is the expected behavior?
I expect that an element of 35px width/height with border-radius: 50%, and box-sizing: border-box and border-width: 17px to work.

I also expect transitions (on hover) from border-width:1px to border-width:17 or border-width:17.5px  to work.

The goal is to have the borders grow inward to fill the entire space of the element.

What went wrong?
When hovering over the each of the elements in the codepen:
1. Element 1 behaves just fine, when the border-width is smaller than 17px.
2. Element 2 misbehaves; instead of the transition finishing and displaying a 35px round green element (the border color), we just see a small black circle (this is undesired)
3. Element 3 misbehaves, there is a flicker while transitioning
4. Element 4 misbehaves, there is a flicker while transitioning.
5. Element 5 misbehaves, even with no transition, because the border width is set to 17px flat, and I am not seeing any border.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 62.0.3202.94  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

This is not an issue in Safari, Firefox, or high-dpi displays with Chrome.
This was tested across 4 computers running the latest OS X.
 
Screen Recording 2017-11-28 at 04.16 PM.mov
129 KB Download

Comment 1 by nainar@chromium.org, Nov 29 2017

Labels: Needs-Feedback
Hi could you provide details of the device you are using? The hardware specs that is. So that we can try to match them to repro. Thank you!
Labels: Needs-Triage-M62

Comment 3 by mivan...@gmail.com, Nov 29 2017

These are the computer specs:
MacBook Pro (Retina, 15-inch, Mid 2014)
2.5 GHz Intel Core i7
16 GB 1600 MHz DDR3
NVIDIA GeForce GT 750M 2048 MB
Intel Iris Pro 1536 MB

These are the connected display specs:
Apple LED Cinema Display
27-inch (2560 x 1440)
NVIDIA GeForce GT 750M 2048 MB graphics
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 29 2017

Cc: nainar@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "nainar@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by mivan...@gmail.com, Nov 29 2017

This is not an issue on the built in laptop display, these are the specs of the laptop display:
Built-in Display
15.4-inch (2880 x 1800)
NVIDIA GeForce GT 750M 2048 MB

The issue appears when moving a browser window from the laptop screen to the low-res screen, and the issue disappears when moving the browser window back to the built in laptop screen.

Comment 6 by mivan...@gmail.com, Nov 29 2017

This issue is also present on this display:
vp2770 2560x1440
Resolution: 2560 x 1440
Brand: ViewSonic
Size: 27 in

Comment 7 by nainar@chromium.org, Nov 30 2017

Labels: Needs-Bisect
Status: Untriaged (was: Unconfirmed)
Cc: divya.pa...@techmahindra.com
Labels: -Type-Bug -Pri-2 -Needs-Bisect hasbisect-per-revision Triaged-ET M-64 Pri-1 Type-Bug-Regression
Owner: enne@chromium.org
Status: Assigned (was: Untriaged)
Able to reproduce the issue on reported version 62.0.3202.94, latest Canary 64.0.3280.0 using Mac 10.12.6
Note: Issue is not seen on Ubuntu 14.04 and Windows 10

Bisect Info:
================
Good Build: 59.0.3071.86 
Bad Build: 60.0.3072.0

CHANGELOG URL:
You are probably looking for a change made after 464700 (known good), but no later than 464701 (first known bad).
https://chromium.googlesource.com/chromium/src/+log/d1040f6d95719c52a3ec442c76be29d5c0630bf4..e594588348ea08e4cdc15dc587efa5645db5023e

suspect: https://codereview.chromium.org/2768143002

Suspecting same from changelog.

@enne: Please confirm the issue and help in re-assigning if it is not related to your change.

Thanks!


Comment 9 by enne@chromium.org, Nov 30 2017

Owner: bsalomon@chromium.org
I can repro this locally on my lodpi mac (without moving windows across screens). The issue appears to only happen when gpu rasterization is turned on.  bsalomon, can you triage this?
Status: Fixed (was: Assigned)
This was fixed in this change:

https://skia.googlesource.com/skia.git/+/6574921253197338f879130ed99fb9ce483976de

Sign in to add a comment