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

Issue 765848 link

Starred by 5 users

Issue metadata

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



Sign in to add a comment

DirectWrite and ClearType not kicking in for the the find bar

Reported by mqu...@gmail.com, Sep 15 2017

Issue description

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

Steps to reproduce the problem:
1. Use a high-dpi display with DPI set to 150% under Windows 10 Creators Update (must be this version and this DPI, Windows 10 Creators Update made changes to the High DPI rendering)
2. Run Microsoft ClearType wizard and custom the configuration. Exact customization does not matter, but the important thing is to change it from the default.
3. Navigate to the following JSFiddle and run it: https://jsfiddle.net/46c22ovc/
4. Ctrl+F then type "Hello world " into the find-in-page input box.
5. Study the difference in font rendering between what is displayed in the JS Fiddle HTML output and in the find-in-page input box.

What is the expected behavior?
Chrome currently (correctly) uses DirectWrite (and thereby ClearType) for the rendered HTML. It should do the same for the non-HTML elements in the UI.

What went wrong?
The rendered browser Chrome text uses some other method of text rendering that does NOT match what is used in the HTML rendering or what the system is configured for.

Did this work before? N/A 

Chrome version: 63.0.3216.0  Channel: canary
OS Version: 10.0
Flash Version: 

This affects UI components such as the search bar and the "are you sure you want to resubmit this form" dialog. 

This was originally incorrectly filed as #756558
 

Comment 1 by mqu...@gmail.com, Sep 15 2017

Attached the screenshot.
Chrome No DirectWrite for Chrome.png
24.9 KB View Download
Cc: brajkumar@chromium.org
Labels: Needs-Feedback Needs-Triage-M63
Unable to reproduce this issue on Windows-10 Dell precision M3800 (HiDPI) using chrome latest canary #63.0.3218.0 by following steps mentioned below.

1. Opened system settings and set DPI to 150%
2. Navigated to https://jsfiddle.net/46c22ovc/
3. Pressed Ctrl+F and searched for Hello World
4. Observed Hello World gets matched and highlighted 

mqudsi@ Could you please confirm is the above steps is the right way to reproduce this issue? If yes, please check the same on incognito mode or create a new profile under chrome://settings.

Thanks!


765848.PNG
50.4 KB View Download

Comment 3 by mqu...@gmail.com, Sep 21 2017

Sorry, that should have been "set the DPI to 125%", not 150%. It does occur under 150%, but it's not as obvious as at 125%.

_However_ note that I can see (to some extent) the behavior described in the original ticket in the screenshot you posted (765848.PNG). Notice how the rendering of "hello wor" in the search box differs from that of "Hello world" in the HTML document body. 

Make sure you are using a hi-dpi monitor to look at the screenshots. You won't be able to see the difference if you are not using a 4k monitor. 

Here's a zoomed in screenshot of your screenshot; notice the difference between how "hello wor" is rendered and the "sign in" next to it in the background was rendered.
zoomed in.png
11.2 KB View Download
Project Member

Comment 4 by sheriffbot@chromium.org, Sep 21 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: -UI UI>HighDPI
Labels: Triaged-ET
Requesting someone from the inhouse team to take a look at this on High-DPI system.
Cc: pnangunoori@chromium.org
Labels: Needs-Feedback
Tested on Windows-10 Dell precision M3800 (HiDPI) using chrome latest canary #64.0.3241.0 and unable to reproduce the issue even by changing the DPI to 125%. Please refer the screencast for reference.

@mqudsi-- Could you please try by removing the extensions and creating a new profile to verify if the issue still persists. You can also try by updating your Canary to latest version.

Please let us know if we have missed anything.

Thanks in advance.
765848.mp4
1.8 MB View Download

Comment 7 by mqu...@gmail.com, Oct 18 2017

Hello @pnangunoori,

Thanks for sharing the screencast video. Please notice the rendering of the text in the search box, the font kerning differs from that in the rest of the browser interface (chrome) and rendered content (html).

The bug is visible in the video you uploaded, the text in the "find in page" search box is not crisp and isn't being hinted correctly.
Project Member

Comment 8 by sheriffbot@chromium.org, Oct 18 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: sandeepkumars@chromium.org
Can someone from UI>HighDPI team, please look into this issue as this issue is not reproducible from TE end.

Thanks!!
Cc: bsep@chromium.org
Components: UI>Browser>FindInPage
Possible duplicate of  crbug.com/666357  ?
 Issue 666357  is not visible to the public.
I've made 666357 public; there does not appear to be a reason for it to be private.

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

Labels: -Needs-Triage-M63
Owner: bsep@chromium.org
Status: Assigned (was: Unconfirmed)

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

Cc: ajha@chromium.org
 Issue 666357  has been merged into this issue.

Comment 15 by mqu...@gmail.com, Nov 27 2017

If you look at the blown-up comparison between the two texts (in the find text box and in the rendered HTML) you can see that the find text box is using ClearType (the colored artifacts stemming from the ClearText algorithm which uses RGB hinting) vs the 2-color palette used in the rendered HTML, where Direct2D/DirectWrite text rendering is used (which does not directly use ClearType and does not have the same colored artifacts when blown up).

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

Summary: DirectWrite and ClearType not kicking in for the the find bar (was: DirectWrite and ClearType not kicking in for the the browser chrome)
From the duped bug: this is present on Windows 7 as well.

Comment 17 by mqu...@gmail.com, Feb 20 2018

This may be an artifact of #806351, but it should still be kept as a separate bug since it can be worked around separately.
Cc: mmanchala@chromium.org
Labels: Hotlist-DesktopUIChecked
Status: WontFix (was: Assigned)
*** UI Mass Triage *** 

Closing, since there is no updates since the past few weeks. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue.

Sign in to add a comment