Changeset 188569 in webkit

Timestamp:

Aug 17, 2015 7:44:14 PM (9 years ago)

Author:

mmaxfield@apple.com

Message:

Follow up patch after r188566

File:

• trunk/Source/WebCore/ChangeLog (modified) (1 diff)

trunk/Source/WebCore/ChangeLog

@@ -23 +23 @@
         Reviewed by Dan Bernstein.
 
-        WebKit maintains a cache of code point to glyph mapping for a particular font. One of
-        the ways WebKit populates this cache is to create a string holding consecutive code
-        points, create a CTLineRef from the string, and use CTRunGetGlyphs() with
-        CTRunGetStringIndices() to map from the code points to the glyphs. This approach is
-        fundamentally incorrect, as it will combine consecutive code points together in the
-        string if possible to produce a glyph.
-
-        The only way WebKit will ever trigger this code path is if we are inspecting a
-        composite font, first introduced in [1]. These composite fonts are extremely rare
+        Composite fonts were first introduced in [1]. These composite fonts are extremely rare
         because:
         1. None of the preinstalled fonts on either OS X nor iOS are composite fonts,