-
Notifications
You must be signed in to change notification settings - Fork 20.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IE & Edge crash with "Permission denied" on the contents() for <frame />
test
#4441
Comments
Unfortunately, while in the vast majority of cases the test case fails in IE, when you run that particular test in isolation it almost never fails. This makes debugging tricky. |
contents() for <frame />
testcontents() for <frame />
test
Some conclusions from my investigation:
|
I found the cuplrit. IE/Edge sometimes crash when comparing documents between frames... but only if one of the strict equality operators ( This means the issue might as well exist on 3.x as well, maybe it just triggers the condition less often. I'm changing the milestone to 3.4.2 & I'll submit a PR to Sizzle as well. |
…crashes IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Fixes jquerygh-4441
jQuery PR (for jQuery 4.0): #4471. |
…crashes IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Fixes jquerygh-4441
Note to self: reopen issue after landing #4471 so that a Sizzle PR also lands. |
…crashes IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Fixes jquerygh-4441
…crashes IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Fixes jquerygh-4441
…crashes IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Fixes jquerygh-4441
Reopening as we still need to land a fix in Sizzle & then update Sizzle on the |
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. The change to shallow comparisons in `src/selector.js` was done in jquerygh-4471 but relevant changes in `src/selector/uniqueSort.js` were missed. Fixes jquerygh-4441 Closes jquerygh-4471
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Fixes jquery/jquery#4441 Closes jquery/jquery#4471
Sizzle PR: jquery/sizzle#459. |
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Fixes jquery/jquery#4441 Closes jquery/jquery#4471
Re-opening as we still need a new Sizzle with the fix for jQuery 3.x. The Sizzle PR: jquery/sizzle#459 has been merged. |
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. The change to shallow comparisons in `src/selector.js` was done in jquerygh-4471 but relevant changes in `src/selector/uniqueSort.js` were missed. Fixes jquerygh-4441 Closes jquerygh-4471
Reopening since we still need to update Sizzle in jQuery 3.x. |
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. The change to shallow comparisons in `src/selector.js` was done in jquerygh-4471 but relevant changes in `src/selector/uniqueSort.js` were missed. Fixes jquerygh-4441 Closes jquerygh-4471
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. The change to shallow comparisons in `src/selector.js` was done in jquerygh-4471 but relevant changes in `src/selector/uniqueSort.js` were missed. Those changes have landed in Sizzle in jquery/sizzle#459. Fixes jquerygh-4441 Closes jquerygh-4471 Ref jquery/sizzle#459
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. The change to shallow comparisons in `src/selector.js` was done in gh-4471 but relevant changes in `src/selector/uniqueSort.js` were missed. Those changes have landed in Sizzle in jquery/sizzle#459. Fixes gh-4441 Closes gh-4512 Ref gh-4471 Ref jquery/sizzle#459
Fixes jquerygh-4424 Fixes jquerygh-4435 Fixes jquerygh-4441 Fixes jquerygh-4453
Sizzle update merged in #4641. The issue is now fixed both on |
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Ref jquerygh-4441 Ref jquerygh-4471 Ref jquery/sizzle#459
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Ref jquerygh-4441 Ref jquerygh-4471 Ref jquery/sizzle#459
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Ref jquerygh-4441 Ref jquerygh-4471 Ref jquery/sizzle#459
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Ref jquerygh-4441 Ref jquerygh-4471 Ref jquery/sizzle#459
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Ref jquerygh-4441 Ref jquerygh-4471 Ref jquery/sizzle#459
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Ref jquerygh-4441 Ref jquerygh-4471 Ref jquery/sizzle#459
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Ref jquerygh-4441 Ref jquerygh-4471 Ref jquery/sizzle#459
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Ref jquerygh-4441 Ref jquerygh-4471 Ref jquery/sizzle#459
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Ref jquerygh-4441 Ref jquerygh-4471 Ref jquery/sizzle#459
Description
IE 11 as well as Edge (even 17-18) often crash on the
traversing: contents() for <frame />
test with the "Permission denied" error. IE crashes way often than Edge. This is probably related to my Sizzle removal PR (#4395) but I wasn't able to pinpoint the exact reason so far. The error points to line174
insrc/selector.js
. An example failing run: http://swarm.jquery.org/result/3337866.It's hard to debug as it's clearly a race condition. If I run this test in isolation, it always passes.
I think I've seen a similar failure on the
3.4-stable
branch as well but it was happening way less often.We should figure this out before the
4.0.0
release.Link to test case
N/A, it's a core test already in the repo.
The text was updated successfully, but these errors were encountered: