[Webkit-unassigned] [Bug 141576] New: MiniBrowser doesn't use accelerated drawing in WebKit2 windows if a WebKit1 window was opened first
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Feb 13 14:18:59 PST 2015
https://bugs.webkit.org/show_bug.cgi?id=141576
Bug ID: 141576
Summary: MiniBrowser doesn't use accelerated drawing in WebKit2
windows if a WebKit1 window was opened first
Classification: Unclassified
Product: WebKit
Version: 528+ (Nightly build)
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebKit2
Assignee: webkit-unassigned at lists.webkit.org
Reporter: thorton at apple.com
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.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150213/c7e85906/attachment-0002.html>
More information about the webkit-unassigned
mailing list