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

Issue 798641 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Omnibox dropdown text is fuzzy with DPI >= 120

Reported by cesp...@gmail.com, Jan 3 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36

Steps to reproduce the problem:
1. Type text in the omnibox to summon the dropdown window

What is the expected behavior?
The text inside the omnibar dropdown window looks crisp.

What went wrong?
I'm on a high DPI monitor. Using my desktop environment (XFCE), if set my system DPI to 120 or higher, then the text inside the omnibox dropdown is fuzzy. If it is below 120, then that text is crisp.

This does not affect text elsewhere, such as the text inside the omnibox itself, tab titles, or on the webpage.

In the first screenshot, my DPI is set to 120 and the omnibox dropdown text is fuzzy.

In the second screenshot, my DPI is set to 119 and the omnibox dropdown text is crisp.

Did this work before? N/A 

Chrome version: 63.0.3239.108  Channel: stable
OS Version: Ubuntu 16.04
Flash Version: 

I believe this issue is related to https://bugs.chromium.org/p/chromium/issues/detail?id=484400. That's where I learned about the 120 / 1.2 threshold.
 
screen_20180102182254.png
69.0 KB View Download
screen_20180102182307.png
58.9 KB View Download
Cc: vamshi.k...@techmahindra.com
Labels: Needs-Feedback Triaged-ET Needs-Triage-M63
Unable to reproduce the issue on reported chrome version 63.0.3239.108 and on the latest canary 65.0.3309.0 using Windows 10 with the below mentioned steps.
1. Launched chrome
2.Typed some text in Omni box

We have set the Custom scaling to 120. We didn't observe any fuzzy text. Attaching the screen cast of the same.

@Reporter: Could you please check the screen cast and let us know if we have missed any steps while reproducing the issue. Any further inputs from your end helps us to triage it in a better way.

Thanks! 
798641.mp4
1.2 MB View Download
Cc: osh...@chromium.org
Components: UI>HighDPI
+owner of  issue 484400  as fyi

Comment 3 by cesp...@gmail.com, Jan 3 2018

Hi! Thanks for taking a look.

I can confirm that this bug does not reproduce on Windows or macOS, so it seems to be Linux-specific.

Please try to reproduce on a Linux machine, preferably with a high DPI monitor.
Project Member

Comment 4 by sheriffbot@chromium.org, Jan 3 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Unable to reproduce the issue on reported chrome version 63.0.3239.108 and on the latest canary 65.0.3310.0 using Ubuntu 17.10 High DPI machine with steps mentioned below
1. Changed scale value to 200%
2. Launched chrome reported version
3. Typed text in omni bar, text inside the omnibar dropdown window looks crisp

@Inhouse:
As the reporter raised this issue on Ubuntu 16.04, can anyone from the inhouse team have a look atthis issue, hence adding the label as TE-NeedsTriageFromHYD

Thanks!
798641.png
524 KB View Download
Cc: viswatej...@techmahindra.com sc00335...@techmahindra.com
Labels: TE-NeedsTriageFromHYD
Labels: -TE-NeedsTriageFromHYD TE-NeedsTriageFromMTV
HiDPI Linux machines are currently unavailable with HYD in house team to check this issue, requesting some one from MTV team to look in to this issue.
Cc: derat@chromium.org malaykeshav@chromium.org
malaykeshav@ and derat@ - is this older bug moot?  (I see a lot of related changes in  bug 839214 .)
We do not need a HighDpi machine to test this.
This can be tested by adding the command line flag 
'--force-device-scale-factor=1.2' 

(The fix for  bug 839214  is essentially a revert of a change that was landed in april. The same change that was meant to fix the current issue)

Comment 10 by ajha@chromium.org, May 18 2018

Labels: -TE-NeedsTriageFromMTV
Components: -UI UI>Browser>Omnibox

Comment 12 by cesp...@gmail.com, May 25 2018

Hi! I'm on Chrome 66 now and the issue no longer reproduces. I think this can be closed.
Status: Fixed (was: Unconfirmed)
Thanks for letting us know!

Sign in to add a comment