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

Issue 760432 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
derat@chromium.org
█ nona@chromium.org
js...@chromium.org
msw@chromium.org
drott@chromium.org
editing-dev@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

MUSICAL SYMBOL G CLEF should not have grapheme boundary in it

Project Member Reported by mpear...@chromium.org, Aug 30 2017 
While working on a change to RenderText, we noticed that the UTF-8 bytestring for MUSICAL SYMBOL G CLEF (\xF0\x9D\x84\x9E) '𝄞' is allowed to be broken after \xF0.  This character seems to be latin small letter eth 'ð', which doesn't seem like an shortened part of the full character.  I don't think we should allow breaks in this grapheme.

For the context of mws@'s discovery of this, see this message,
https://chromium-review.googlesource.com/c/chromium/src/+/611789#message-8c0d7f8c56730fb0d8cc71b7d20617d7a801183b
and the following one.

Comment 1 by mpear...@chromium.org, Aug 30 2017

Cc: tkent@chromium.org drott@chromium.org msw@chromium.org nona@chromium.org
Since this isn't my area at all, CCing several folks who may want to pick this up, or at least know better how to direct this bug.

Comment 2 by tkent@chromium.org, Aug 30 2017

Cc: -tkent@chromium.org

Comment 3 by yosin@chromium.org, Aug 30 2017

Components: -Blink>Editing Blink>Editing>Selection
Status: Available (was: Untriaged)

Comment 4 by drott@chromium.org, Aug 30 2017

Cc: derat@chromium.org
I don't think there is a grapheme boundary problem within the MUSICAL SYMBOL G CLEF, rather some encoding mixup. ð is U+00F0, it's UTF-16 representation is C3 B0. 𝄞 is F0 9D 84 9E in UTF-8.

Comment 5 by derat@chromium.org, Aug 30 2017

Cc: js...@chromium.org
Sorry, I don't have any ideas about this either.

Comment 6 by mpear...@chromium.org, Feb 8 2018

Status: WontFix (was: Available)
I think msw@ discovered this was an encoding problem, as drott@ thought.

Closing.
►

Sign in to add a comment