Make FontCascade::s_codePath thread safe
Created attachment 446305 [details] Patch
Comment on attachment 446305 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=446305&action=review > Source/WebCore/ChangeLog:3 > + Make FontCascade::s_codePath thread safe Can we just delete it instead?
Created attachment 446658 [details] Patch
(In reply to Myles C. Maxfield from comment #2) > Can we just delete it instead? Let's try. It involves more code removal than I thought.
<rdar://problem/86506735>
Comment on attachment 446658 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=446658&action=review I think this is right but I think we should run this by a GTK port contributor before landing. > Source/WebCore/ChangeLog:14 > + - making the Gtk port go back to effectively using CodePath::Auto I thought the GTK port _only_ had the complex text codepath. Maybe I'm misinformed?
Pull request: https://github.com/WebKit/WebKit/pull/4242