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.
<rdar://problem/25304548>
Created attachment 274767 [details] Patch
Comment on attachment 274767 [details] Patch Do we use these defaults in WTR?
(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.
http://trac.webkit.org/changeset/198593