Bug 150051

Summary: [Font Features] Tiny cleanup regarding FontCascade::typesettingFeatures()
Product: WebKit Reporter: Myles C. Maxfield <mmaxfield>
Component: New BugsAssignee: Myles C. Maxfield <mmaxfield>
Status: RESOLVED FIXED    
Severity: Normal CC: dino, jonlee, simon.fraser, thorton, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch simon.fraser: review+

Myles C. Maxfield
Reported 2015-10-12 15:05:17 PDT
[Font Features] Tiny cleanup regarding FontCascade::typesettingFeatures()
Attachments
Patch (2.64 KB, patch)
2015-10-12 15:06 PDT, Myles C. Maxfield
simon.fraser: review+
Myles C. Maxfield
Comment 1 2015-10-12 15:06:23 PDT
Simon Fraser (smfr)
Comment 2 2015-10-12 15:24:10 PDT
Comment on attachment 262925 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=262925&action=review > Source/WebCore/platform/graphics/FontCascade.cpp:610 > +#if !PLATFORM(COCOA) > + if (run.length() > 1 && typesettingFeatures()) > return Complex; > +#endif We have FontCascadeCocoa; can't this be done in that file, instead of having an #ifdef?
Myles C. Maxfield
Comment 3 2015-10-12 15:39:54 PDT
Comment on attachment 262925 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=262925&action=review >> Source/WebCore/platform/graphics/FontCascade.cpp:610 >> +#endif > > We have FontCascadeCocoa; can't this be done in that file, instead of having an #ifdef? I think in this case, it would be worse. This thing is so simple that adding another function with two implementations is worse than this tiny ifdef.
Myles C. Maxfield
Comment 4 2015-10-12 15:41:12 PDT
Radar WebKit Bug Importer
Comment 5 2015-12-04 15:22:29 PST
Note You need to log in before you can comment on or make changes to this bug.