New issue
Advanced search Search tips

Issue 620629 link

Starred by 11 users

Issue metadata

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



Sign in to add a comment

Misdisplays single characters "Not Identical To" and "Not Almost Equal To"

Reported by a.br...@gmail.com, Jun 16 2016

Issue description

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

Example URL:
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=%E2%89%A2%E2%89%89

Steps to reproduce the problem:
1. Insert ≢ (U+2262) and ≉ (U+2249) in the address bar or any edit field on any page.

What is the expected behavior?
A display similar to ̸≡ (U+0338,U+2261) and ̸≈ (U+0338,U+2248).

What went wrong?
Renders as ≢ (U+2261,U+0338) and ≉ (U+2248,U+0338).

Does it occur on multiple sites: Yes

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? Yes 

Chrome version: 51.0.2704.84  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 21.0 r0
 
Components: -Blink Blink>Fonts

Comment 2 by e...@chromium.org, Jun 21 2016

Status: WontFix (was: Unconfirmed)
These render as per the default font. In cases where they are incorrect or hard to distinguish that is a problem with the font and not with Chrome.

Comment 3 by a.br...@gmail.com, Jun 21 2016

Opening https://jsfiddle.net/07ptngz5/ in various browsers (and using the character with the same fonts in other Windows applications) shows that the issue is not with the font. Opera has the same issue, but Safari and Firefox do not, so it is clearly a Blink for Windows issue.
Fail.png
129 KB View Download

Comment 4 by a.br...@gmail.com, Jul 27 2016

Blink has the same issue with ↚ ↛ ↮ (U+219A U+219B U+21AE).

Comment 5 by a.br...@gmail.com, Jun 12 2017

And also ≮ ≯ (U+226E U+226F).

Comment 6 by a.br...@gmail.com, Jun 12 2017

And also ≰ ≱ (U+2270 U+2271)
I don't understand how you can claim that this is "a font issue", given the evidence presented. Can you justify this position?

Comment 8 by k...@aplteam.com, Oct 29 2017

?????

Sign in to add a comment