Some Hangul consonants (U+114C, U+112B, etc) are not combined with other Hangul combining jamos

• Component: Layout and Rendering
• Status: RESOLVED MOVED

[Jungshik Shin]

Created attachment 241364 [details]
Left: correct (Chrome 41), Right: Incorrect (Safari 7.1)

OS: Mac OS 10.9
Safari: Version 7.1 (9537.85.10.17.1)

Reproduction step:

1. Install 'NotoSansCJK' (either SuperOTC or Regular OTC) available at http://www.google.com/get/noto/cjk.html
2. Start Safari
3. Go to the following URL
   data:text/html;charset=utf-8,<span%20style="font-family:%20Noto%20Sans%20CJK%20KR;">ᅌᅥᆫᄫᅳᆯ&#x1147;&#x116e;</span>

Expected (see the attachment) 

You see three syllables the first which are made up of three Hangul combining Jamos and the last of which is made of two Hangul Jamos 

Actual (see the screenshot )
Three Jamos enumerated linearly for the first two syllables and two Jamos enumerated linearly for the last syllable. 

Additional information:

Jamos in the step 3 are:

U+114C U+1165 U+11AB
U+112B U+1173 +U11AF
U+1147 U+116E

A more comprehensive example is found at http://ko.wikisource.org/wiki/훈민정음언해 where most combinations are rendered correctly, but some syllables starting with consonants such as U+114C, U+112B and U+1147 are incorrectly shaped. (there are a couple of other issues, but I'll file them separately)

Chrome 38.x (that also uses CoreText) has the same issue, but Chrome 40.x (that switched to use harfbuzz) does not have this issue any more.

[Radar WebKit Bug Importer]

<rdar://problem/18952844>

[Myles C. Maxfield]

This occurs in TextEdit as well on OS X, so the problem is in CoreText.

[Brent Fulgham]

The fix for this issue was needed outside the WebKit project, therefore this is being resolved as 'Moved'.

This should now be fixed in shipping software.