RESOLVED FIXED 141576
MiniBrowser doesn't use accelerated drawing in WebKit2 windows if a WebKit1 window was opened first 
https://bugs.webkit.org/show_bug.cgi?id=141576
Summary MiniBrowser doesn't use accelerated drawing in WebKit2 windows if a WebKit1 w...
Tim Horton
Reported 2015-02-13 14:18:59 PST
WebKit1 registers a huge dictionary of NSUserDefaults, including WebKitAcceleratedDrawingEnabled=NO. In WebKit2, the acceleratedDrawingEnabled pref defaults to true, but we first read debug prefs (one of which is WebKitAcceleratedDrawingEnabled) from NSUserDefaults. So, if you have a process where WebKit1 and WebKit2 coexist, and WebKit1 is set up first, you'll end up with accelerated drawing off by default in subsequently created WebKit2 views despite the WebKit2 default intending to have that preference on.
Attachments
Patch (1.61 KB, patch)
2016-03-23 12:07 PDT, Tim Horton 		simon.fraser: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Tim Horton
Comment 1 2016-03-23 00:09:24 PDT
<rdar://problem/25304548>
Tim Horton
Comment 2 2016-03-23 12:07:45 PDT
Created attachment 274767 [details] Patch
Simon Fraser (smfr)
Comment 3 2016-03-23 12:09:38 PDT
Comment on attachment 274767 [details] Patch Do we use these defaults in WTR?
Tim Horton
Comment 4 2016-03-23 12:15:43 PDT
(In reply to comment #3) > Comment on attachment 274767 [details] > Patch > > Do we use these defaults in WTR? Doesn't appear so. WKTR uses the preferences API.
Tim Horton
Comment 5 2016-03-23 14:06:55 PDT
http://trac.webkit.org/changeset/198593
Note You need to log in before you can comment on or make changes to this bug.