155786 2016-03-23 03:15:42 -0700 WebKit nightly uses the built-in Safari engine instead of its own on OS X 10.11.4 El Capitan 2016-03-23 09:02:22 -0700 1 1 1 Unclassified WebKit New Bugs WebKit Nightly Build Mac OS X 10.11 RESOLVED MOVED InRadar P2 Normal --- 1 m.goleb+bugzilla webkit-unassigned timothy oldest_to_newest 1177324 0 m.goleb+bugzilla 2016-03-23 03:15:42 -0700 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. :( 1177355 1 timothy 2016-03-23 08:42:30 -0700 Sorry for the trouble. Unfortunately we have no way to fix this at the Webkit level, so I will close this bug. The issue is being looked at inside Apple. We are exploring a fix for this in a software update, but until then you can apply the following updated workaround: https://trac.webkit.org/wiki/WebKitNightlyElCapWorkaround <rdar://problem/25296908>