[Webkit-unassigned] [Bug 149346] New: WebKit nightly uses the built-in Safari engine instead of its own

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Sep 18 09:07:54 PDT 2015


            Bug ID: 149346
           Summary: WebKit nightly uses the built-in Safari engine instead
                    of its own
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Macintosh
                OS: Mac OS X 10.11
            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 beta (I'm now using the GM candidate) 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.

Reported originally at https://twitter.com/m_gol/status/639445068731035648.

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/20150918/d39138e0/attachment.html>

More information about the webkit-unassigned mailing list