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

Issue 689599 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
kojii@chromium.org
e...@chromium.org
█ tabatkins@chromium.org
drott@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Feature



Sign in to add a comment

Render something when font has no glyph for some code point

Project Member Reported by zcorpan@gmail.com, Feb 7 2017 
From https://bugs.chromium.org/p/chromium/issues/detail?id=530342#c15

> Looks like there is no difference.

https://bugs.chromium.org/p/chromium/issues/detail?id=530342#c16

> Most likely, because we just render these code points, glyphs are not defined in the font you're using? This patch does not add support to render missing glyphs such as hex-display.

Test: http://jsbin.com/wamerawapu/edit?html,js,output

The change in that issue has now reached Stable I believe, but no visual change (for most users?). I thought the point of the change was to render *something* ("must be rendered as a visible glyph").

In Firefox on macOS Sierra I get boxes with hex numbers, see attachment.
firefox-control-characters.png
64.8 KB View Download

Comment 1 by e...@chromium.org, Feb 7 2017

Cc: drott@chromium.org
Labels: -Type-Bug OS-Android OS-Chrome OS-Linux OS-Mac OS-Windows Type-Feature
Status: Available (was: Untriaged)
zcorpan: The point of the change discussed in  issue 530342  is to preserve and render control characters when present in the font. This allows data transfer such as copy and paste to preserve control characters.

Rendering the codepoint in hexadecimal for missing glyphs, like Firefox, is something we'd like to do eventually but outside the scope of  issue 530342 .

I thought we had a bug tracking that but can't find it, let's use this one for now. Thanks for the report!
Project Member

Comment 2 by sheriffbot@chromium.org, Feb 12 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by e...@chromium.org, Feb 12 2018

Status: Available (was: Untriaged)
►

Sign in to add a comment