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

Issue 723969 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Borders on elements appear darker/blurry/hazy (happened after latest update)

Reported by hmale...@gmail.com, May 18 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Example URL:
http://getbootstrap.com/css/

Steps to reproduce the problem:
1. Navigate to any site and check the borders of elements
2. As an example check the bootrap site
3. Used to work fine bu the borders now appear darker/blurry/...

What is the expected behavior?
Borders should be crisp like they were before the latest chrome update

What went wrong?
Borders on elements appear darker/blurry/hazy (happened after latest update)
Borders should be crisp like they were before the latest chrome update

Note: I am on a Surface pro 4, not sure if this is an issue attributed to High DPI displays.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes 

Does this work in other browsers? Yes

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 10.0
Flash Version:
 
Chromeborderissue.png
218 KB View Download
Cc: ligim...@chromium.org
Labels: -Pri-2 Needs-Bisect Needs-Triage-M58 Pri-1

Comment 2 by hdodda@chromium.org, May 19 2017

Cc: hdodda@chromium.org
Labels: -Type-Bug -Needs-Bisect hasbisect-per-revision M-60 Type-Bug-Regression
Owner: ka...@opera.com
Status: Assigned (was: Unconfirmed)
Issue is reproduced only on windows 10 machine with high Dpi using chrome stable M58 #58.0.3029.110 and canary M60 #60.0.3103.0 .

This is a regression issue broken in M58 .

Using the per-revision bisect providing the bisect results,
Good build: 58.0.3010.0 (Revision: 449855).
Bad build: 58.0.3012.0 (Revision: 450199).

You are probably looking for a change made after 449940 (known good), but no later than 449947 (first known bad).

CHANGELOG URL:

 https://chromium.googlesource.com/chromium/src/+log/7a8b621535abb3aa5d9c0ff2196299f1d90449a5..28ff32abc83ae8939f56702151b3d982859d56b5

From the CL above, suspecting the following Cl and assigning the issue to the concern owner 

Suspect CL : https://chromium.googlesource.com/chromium/src/+/934becac5daa91ea979fb66e4ae21761ca11ebc9

@karlo- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Review-Url: https://codereview.chromium.org/2640143005

Thanks!
Components: -Blink Blink>Paint
Labels: -Pri-1 -M-60 -Needs-Triage-M58 BugSource-User PaintTeamTriaged-20170519 Pri-2
This is not a P1 because the border is still there in the right place. It is somewhat ugly, however, and maybe there remain problems with zooming the sub-pixel positioned borders.

Comment 4 by ka...@opera.com, May 19 2017

This is probably because you are using a high dpi device, with a device scale factor of 150%-200%.  If so, this is the expected behavior; the border will be zoomed by the same factor, and if it's between 1.5 and 2, it will be rounded up to two.

All else being equal, the current rendering should be the same as MS Edge, can you possibly verify that?

Comment 5 by hmale...@gmail.com, May 19 2017

Yes thats right like i mentioned i am on ahigh DPI device (Surface pro 4) with scaling set to 150% (1.5 i guess)

And yes the rendering is same on MS Edge!

Having said that, what changed now which caused this to happen? Because the un-scaled (am i right ?) borders looked crisper

Comment 6 by ka...@opera.com, May 29 2017

Chromium 59 changed border sizes to be sub pixel (ie. fractional), in the past they were integer sizes, always rounded down.  With sub pixel rendering, borders that eg. are size 1.5px will be rounded up to 2px.  This should be closer to what the author intended, but does represent a change in behavior.  This is also the behavior of MS Edge.

In any case, this behavior is as expected.

Comment 7 by ka...@opera.com, Feb 28 2018

Owner: karloygard@chromium.org
Status: WontFix (was: Assigned)
Working as intended according to comment #6.

Sign in to add a comment