New issue
Advanced search Search tips

Issue 723934 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Brightness Filter Distorts/Weights Text

Reported by mrcro...@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

Steps to reproduce the problem:
1. Create an element (ie, a div) with some text inside and a background color
2. Set a CSS filter with an increased brightness

What is the expected behavior?
The text inside the element should not be distorted

What went wrong?
The text inside an element with brightness set seems to be distorted and have an increased font weight.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 10.0
Flash Version: 

I happened to encounter this with white on red, and it was fairly obvious, so I've used that as a sample - using a thicker font like Fantasy makes this significantly worse. Firefox and Edge have some distortion, but Chrome is visibly worse (it's especially obvious that the text looks different, and can potentially be borderline unreadable). I've attached a comparison.
 
brightness-test.html
634 bytes View Download
brightness-comparrison.png
17.2 KB View Download
Labels: Needs-Triage-M58 Needs-Bisect
Components: Blink>Compositing>Filters
Labels: -Type-Bug -Pri-2 -Needs-Bisect -Needs-Triage-M58 hasbisect-per-revision M-60 Pri-1 Type-Bug-Regression
Owner: f...@opera.com
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Windows 10 using chrome reported version #58.0.3029.110 and latest canary #60.0.3102.0.
Issue is not reproducible in OS-Mac and OS-Linux.

Bisect Information:
=====================
Good build: 53.0.2773.0    Revision(400610)
Bad Build : 53.0.2776.0    Revision(401299)

Note: Due to unavailability of 53.0.2774.0 and 53.0.2775.0 versions for OS-Win, 53.0.2773.0 has been considered as good build.

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/c6b153cc33b68d86d407911d66b07ec99afb402e..8729c0678b72bdf6cac789df06469573b0716a1d

From the above change log suspecting below change
Review url: https://codereview.chromium.org/2065593002

fs@ - 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.

Thanks...!!

Comment 3 by f...@opera.com, May 18 2017

Labels: -hasbisect-per-revision Needs-Bisect
Owner: krajshree@chromium.org
My CL made the test above work at all, by supporting 'filter' without a prefix. I'm attaching an updated version of the test that should allow for proper bisect. Assigning back for new bisect.
brightness-test.html
684 bytes View Download
Labels: -Pri-1 -Needs-Bisect -Type-Bug-Regression Pri-2 Type-Bug
Owner: ----
Status: Untriaged (was: Assigned)
Able to reproduce this issue on Win-10 using chrome reported version #58.0.3029.110 and latest canary #60.0.3103.0.

This is a non-regression issue as it is observed from M30 old builds. 

Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!
Cc: senorblanco@chromium.org
Components: -Blink>Compositing
Labels: BugSource-User PaintTeamTriaged-20170523
Status: Available (was: Untriaged)
It's worse on Windows than either Linux or Mac. This is a compositor applied filter, I presume.
It may be because filters force subpixel antialiasing (ClearType text on Windows) to be disabled on the unfiltered primitive.

If so, it may be difficult to avoid. Most useful filter chains mess with gamma enough to make subpixel AA wrong, many (e.g., blur) would expose ugly fringing.
Project Member

Comment 7 by sheriffbot@chromium.org, May 24 2018

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.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
Still happens, only on Windows. I have to think this is related to ditching sub-pixel text, which we are not likely to change (it might not even be possible to fix without causing all sorts of other problems).

Sign in to add a comment