[Webkit-unassigned] [Bug 155786] New: WebKit nightly uses the built-in Safari engine instead of its own on OS X 10.11.4 El Capitan
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Mar 23 03:15:42 PDT 2016
https://bugs.webkit.org/show_bug.cgi?id=155786
Bug ID: 155786
Summary: WebKit nightly uses the built-in Safari engine instead
of its own on OS X 10.11.4 El Capitan
Classification: Unclassified
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: New Bugs
Assignee: webkit-unassigned at lists.webkit.org
Reporter: m.goleb+bugzilla at gmail.com
Since I upgraded to the El Capitan 10.11.4 I can't get WebKit nightly to use its own engine:
1. There is no "Check for updates..." in the Safari menu.
2. It uses the built-in Safari 9 engine which can be easily verified by going to http://kangax.github.io/compat-table/es6/ and seeing how the results are identical to Safari 9, not WebKit ones.
3. If I open Safari, close it & then open WebKit I always get the popup with a message: "Your Safari extensions have been migrated.". Every single time.
I haven't had such problems in earlier OS X releases.
This is another incarnation of bug 149346 that appeared in 10.11.0 and was fixed a few months later. The bug is back. :(
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160323/6c43d8f6/attachment-0001.html>
More information about the webkit-unassigned
mailing list