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

Issue 627187 link

Starred by 2 users
Status: WontFix
Owner:
drott@chromium.org
Closed: Jan 2017
Cc:
behdad@chromium.org
kojii@chromium.org
esprehn@chromium.org
█ rnimmagadda@chromium.org
drott@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Not needed notdef glyph when an Arabic diacritic comes after zwnj

Project Member Reported by ebra...@gnu.org, Jul 11 2016 
This is not a really common and real world case but maybe indicates more issue somewhere else thats why I filed it anyway.

Chrome Version       : 51.0.2704.106
OS Version: OS X 10.11.5

What steps will reproduce the problem?
data:text/html;charset=utf8,%D8%A8‌%D9%91

What is the expected result?
Same with:
data:text/html;charset=utf8,%D8%A8%D9%91

What happens instead of that?
I see a ,notdef glyph (rectangle) on first testcase

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36
Screen Shot 2016-07-11 at 11.53.03 PM.png
13.6 KB View Download

Comment 1 by behdad@chromium.org, Jul 11 2016 

Weird.  Looks like a hb-coretext and/or fallback issue.

Comment 2 by e...@chromium.org, Jul 12 2016

Labels: Needs-Feedback
Are you running with experimental web platform features enabled? Might be related to the change to render unicode control characters.

Comment 3 by ebra...@gnu.org, Jul 12 2016

Labels: -Needs-Feedback
I see the issue on latest Canary without any experimental flag (/Applications/Google Chrome Canary.app/Contents/MacOS/Google Chrome Canary --flag-switches-begin --flag-switches-end)

Comment 4 by rnimmagadda@chromium.org, Jul 13 2016

Cc: -e...@chromium.org esprehn@chromium.org rnimmagadda@chromium.org dominik....@intel.com
Labels: -Type-Bug M-52 Type-Bug-Regression
Owner: e...@chromium.org
Status: Assigned (was: Unconfirmed)
====================================

Good Build:

40.0.2172.0   Base Position: 297115


Bad Build:

41.0.2215.0   Base Position: 303403

=====================================

Able to repro this issue on MAC (10.11.5) for the Google Chrome Stable Version - 51.0.2704.106

This is a regression issue broken in M40, below mentioned is the bisect info:

CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/0a65bf2b4d91750ae65cffb669018e6c2444ba2f..2c9345ebf88f2a5431dd18f42611052b846cb142

Suspecting Commit: efe32dde1dcd5b68989b625f456846506a934a58	

Review URL: https://codereview.chromium.org/175253002

@dominik.rottsches/eae: Could you please look into the issue, and if it has nothing to do with your changes and if possible please do assign it to the concerned owner.

Thank you.

Note: Issue observed only on MAC OS.

Comment 5 by e...@chromium.org, Oct 20 2016

Cc: -dominik....@intel.com
Owner: drott@chromium.org

Comment 6 by e...@chromium.org, Jan 27 2017

Status: WontFix (was: Assigned)
No longer reproduces.

Comment 7 by ebra...@gnu.org, Feb 6 2017 

I still see it on "Version 57.0.2987.21 beta (64-bit)". Is that fixed on Canary?
►

Sign in to add a comment