Bug 149346 - WebKit nightly uses the built-in Safari engine instead of its own on OS X 10.11 El Capitan
Summary: WebKit nightly uses the built-in Safari engine instead of its own on OS X 10....
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Mac OS X 10.11
: P2 Normal
Assignee: Nobody
URL:
Keywords:
: 150180 151212 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-09-18 09:07 PDT by Michał Gołębiowski-Owczarek
Modified: 2016-03-23 03:16 PDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Gołębiowski-Owczarek 2015-09-18 09:07:54 PDT 
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.
Comment 1 Timothy Hatcher 2015-09-18 10:29:07 PDT 
The issue is "rootless" prevents DYLD env vars from being used. That is how we point Safari to the WebKit frameworks in the nightly bundle. We are working on a fix, but it will be via a Safari update not a nightly update.
Comment 2 Kevin Decker 2015-10-06 13:43:33 PDT 
Dropping WebKit nightlies from six-speed in light of this (all of my machines are now El Capitan). Will restore when the Safari fix lands.
Comment 3 Alexey Proskuryakov 2015-10-15 20:38:40 PDT 
*** Bug 150180 has been marked as a duplicate of this bug. ***
Comment 4 Alexey Proskuryakov 2015-11-15 13:50:05 PST 
*** Bug 151212 has been marked as a duplicate of this bug. ***
Comment 5 Alexey Proskuryakov 2015-11-15 13:50:43 PST 
https://trac.webkit.org/wiki/WebKitNightlyElCapWorkaround
Comment 6 Alexey Proskuryakov 2016-02-24 20:23:39 PST 
This has been fixed in OS update that shipped a while ago.
Comment 7 Michał Gołębiowski-Owczarek 2016-03-23 03:16:07 PDT 
It used to work and now the bug is back. :( I reported it again as bug 155786.