New issue
Advanced search Search tips

Issue 666357 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue 765848
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Text in Find UI is fuzzy

Project Member Reported by amccarth@google.com, Nov 17 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36

Steps to reproduce the problem:
1. Press Ctrl+F.
2. Type some text to find on the page.

What is the expected behavior?
The Find UI should look similar to the rest of Chrome's UI.

What went wrong?
The Find UI is blurry, as though it's been scaled up.

Did this work before? Yes 53, maybe 52

Chrome version: 54.0.2840.99  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0

My desktop is set to 120 pixels-per-inch, which is 125% of the typical 96 pixels-per-inch.  Most of Chrome seems to do the right thing (now), but the Find UI appears to be stretched, resulting in blurry text.  Attached screenshot shows Incognito, but the same blurring appears in standard mode, so it's not related to the Incognito color scheme.
 
chrome_fuzzy_search_text.png
485 KB View Download
Labels: M-54 Needs-Triage-M54
M54 is not a realistic milestone for a fix, but team is on the process of triaging and will add appropriate Milestone.

Comment 2 by amccarth@google.com, Nov 17 2016

I didn't set the milestone.  It must have been auto-populated by the form.  The form asked what version the problem first appeared in, and I answered 54.
Labels: -M-54 Needs-Bisect M-57
Status: Untriaged (was: Unconfirmed)
Able to reproduce this on Win7/64 bit - Version 54.0.2840.99 m (64-bit)

Tagging with current ToT Milestone label. Please feel free to change it if needed.
666357 on Win7.png
431 KB View Download

Comment 5 by ajha@chromium.org, Nov 22 2016

Cc: ajha@chromium.org
Components: -UI UI>Browser>FindInPage UI>HighDPI
Labels: -Pri-2 -Needs-Bisect -Needs-Triage-M54 hasbisect Pri-1
Owner: bsep@chromium.org
Status: Assigned (was: Untriaged)
Able to reproduce the issue on the latest canary(57.0.2926.0) of Windows-10 as well. The behavior has been behaving the same since 54.0.2800.0 and https://codereview.chromium.org/2157243003 landed.

Regression info:
================

Last good build: 54.0.2800.0
First bad build: 54.0.2802.0(no 54.0.2801.0 build for windows available)

Changelog:
==========
https://chromium.googlesource.com/chromium/src/+log/54.0.2800.0..54.0.2802.0?pretty=fuller&n=10000

Manually inspecting this looks to be related to https://codereview.chromium.org/2157243003 from the above changelog.

Bret@: Could you please take a look at this or help in routing this to appropriate owner.

Thank you!

Comment 6 by bsep@chromium.org, Nov 23 2016

Labels: -Pri-1 Pri-2
It's hard to call this a "regression" because 125% didn't work at all before... but I'll take a look.

If you log out and back in (or just restart the computer) does the problem go away?

Comment 7 by amccarth@google.com, Nov 23 2016

Restarting the computer does not change things.  I've tried on multiple Windows 7 machines.

I'm not sure what you mean by 125% not working "at all before."  I've been using Chrome that way for many years now.  Generally, the text wasn't as large as it was supposed to be, but nothing's been blurry for a very long time before 54.

Comment 8 by bsep@chromium.org, Nov 23 2016

The text was not as large as it was supposed to be because 125% wasn't working. It was enabled in 54, which is why you're seeing some changes.

It's curious that this doesn't show up on Windows 10. Or at least no one has complained about it there. Regardless, I'll take a look at it.
This bug was mentioned as a possible duplicate of  issue 765848  

i. Has there been any progress since November of last year?

ii. Why is this issue restrict-view? I don't see anything confidential, can we remove that label?
s/duplicate of/duplicate for

Comment 11 by bsep@chromium.org, Nov 21 2017

I haven't looked into it. The fact that it reproduces on Windows 10 will make it easier to investigate, but I'm still swamped.

I don't know why it's marked restricted.
Labels: allpublic

Comment 13 by bsep@chromium.org, Nov 27 2017

Mergedinto: 765848
Status: Duplicate (was: Assigned)
Duping into the newer bug because it has more information.
The newer bug report seems to suggest that the scope is more limited.  For example, it claims that it's only in the Creator's edition of Windows 10, whereas this bug shows it goes back to (at least) Windows 7.

Comment 15 by bsep@chromium.org, Nov 27 2017

#14: I would guess the root issue is the same regardless of the OS version. I'll put a note on the newer bug though, to make sure.

Sign in to add a comment