Last modified: 2014-09-05 23:56:28 UTC
From the console: SCRIPT70: Permission denied Main_Page, line 1 character 1 Filing to track this.
So after poking around for a bit I was able to get past this error with the following registry key set to "1": HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN \FeatureControl\FEATURE_PROTOCOL_LOCKDOWN\iexplore.exe Isn't IE support fun? Now the save button (bug #63043) changes color but clicking it results in "SCRIPT70: Permission denied" that IE's debugger says comes from the following line in jquery.js: proxy=function(){ return fn.apply(context,args.concat(core_slice.call(arguments))); }; Hints on registry keys from http://stackoverflow.com/questions/5352057/script70-permission-denied-ie9 Looks like there may be some help in the newer versions of jquery: http://bugs.jquery.com/ticket/13936
*** Bug 63043 has been marked as a duplicate of this bug. ***
Got past part of the permission problem without messing with the registry (yay!) by looking at newer jQuery code and seeing how it avoided use of iframe. It is now stopping in setUpSurface.
Created attachment 14910 [details] diff of changes to update jquery
Updated to latest VE (which shares MW's JQuery?) and saw the problem again. Clicked IE's "Start debugging" in IE9 and wasn't able to reproduce it. Returned to page, clicked IE's "Stop debugging" and then clicked VE's "Edit". Spinner went into infinite loop. Now, what are the dev tools setting up to cause this behavior?
For the record, I haven't experienced this problem in weeks of messing around with VE in IE in either IE10 or IE11.