Microsoft Edge fails the "Iframe dispatch should not affect jQuery (#13936)" test

[mgol]

Microsoft Edge (from the newest Windows 10 build 10130) fails the "Iframe dispatch should not affect jQuery (#13936)" test with an error:

{
  "description": "Permission denied",
  "message": "Permission denied",
  "name": "TypeError",
  "number": -2146828218
}

All others pass if you test modules individually. There are a couple of support tests that now pass (compared to IE11): boxSizingReliable (this one didn't pass in the previous build from April 29), noCloneChecked, optSelected, radioValue. The focusin test now fails, see #2389.

Interestingly enough, if you run the whole test suite it fails a lot more tests; most likely this one leaves the browser in a bad state.

Screenshot:

[mgol]

Note: I added MS Edge support test results in 8e111df & 546593b so that the browser is not erroneously detected as Chrome.

[mgol]

Sizzle issue: jquery/sizzle#339

[gibson042]

@jacobrossi Specifically, this would not be an issue if IE Edge didn't throw "permission denied" when accessing the document of an unloaded iframe; see jquery/sizzle@a431c02 and http://bugs.jquery.com/ticket/13936 .

[mgol]

Specifically, this would not be an issue if IE Edge didn't throw "permission denied" when accessing the document of an unloaded iframe

Yup, especially that we cannot change the code of many older jQuery versions that live in the wild.

[mgol]

For people following, there has been a discussion about that at jquery/sizzle@28f4c67.

[mgol]

I'd mark it as a blocker; it's very simple to revert the additional check and it'd be good to have it in for an alpha.

That'd require a Sizzle update, though, so I'll leave it up to you.

[jacobrossi]

We're tracking fixing this. Unfortunately there's a fairly gnarly issue related to iframe security features we have that make this quite the issue to fix. We're working on stabilizing Edge for the first release, which means a massive change like this isn't appropriate at this time. But we're going to look at fixing this nonetheless after we get the first version out the door.

[mgol]

It's now fixed in Sizzle so I added the "Awaiting Sizzle update" label.