New issue
Advanced search Search tips

Issue 685559 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: 2017-02-13
OS: Windows
Pri: 2
Type: Compat



Sign in to add a comment

Sone lines of the page fonts looks bluer , unreadable , junk

Reported by ronefr...@gmail.com, Jan 26 2017

Issue description

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

Example URL:
https://www.extremetech.com/mobile/243342-samsungs-foundry-business-upcoming-10nm-designs-offsets-catastrophic-note-7-losses

Steps to reproduce the problem:
1. in this URL , scroll slowly up and down 
2. wait few second and you one line or more at the top of the scrolled area look junk
3. 

What is the expected behavior?
Fonts should look regular 

What went wrong?
Sone lines  of the page fonts looks bluer , unreadable , junk

Does it occur on multiple sites: N/A

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? Yes

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

This bug exists many months
 
Capture.JPG
134 KB View Download
Labels: Prestable-56.0.2924.76 Needs-Triage-M56
Cc: pbomm...@chromium.org
Components: Blink>Fonts
Unable to reproduce the issue checked on Windows 7 and 10 with latest Chrome stable i.e., 56.0.2924.76.

Comment 3 by e...@chromium.org, Jan 30 2017

Components: -Blink>Fonts Blink>Paint
Unable to reproduce, looks like a paint issue.
Labels: Needs-Feedback
NextAction: 2017-02-13
This looks like a corrupted composited layer for the scrolling content. The problem may be manifesting now because we have started compositing the scroller on low DPI machines under some circumstances.

Exactly when did this problem start? Have you seen any other problems with GPU intensive applications? Does the problem reproduce for you on any other machines?
Status: WontFix (was: Unconfirmed)
Closing due to a lack of feedback. Please comment again if you have answers to the questions in comment #4.

Sign in to add a comment