Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Core: Drop support for Edge Legacy (i.e. non-Chromium Microsoft Edge)#4792

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
mgol merged 1 commit intojquery:masterfrommgol:drop-edgehtml
Sep 22, 2020

Conversation

mgol
Copy link
Member

Summary

Drop support for EdgeHTML (i.e. non-Chromium Microsoft Edge).

Also, restrict some workarounds that were applied unconditionally in all
browsers to run only in IE now. This slightly increases the size but reduces
the performance burden on modern browsers that don't need the workarounds.

Also, clean up some comments & remove some obsolete workarounds.

Fixesgh-4568

-255 bytes 🎉

Checklist

timmywil and boghyon reacted with hooray emojitimmywil and boghyon reacted with rocket emoji
@@ -543,7 +543,7 @@ jQuery.extend( {
if ( s.crossDomain == null ) {
urlAnchor = document.createElement( "a" );

// Support: IE <=8 - 11+, Edge 12 - 17 only
// Support: IE <=8 - 11+
Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I removed mentions of Edge from support comments as well. Among other things, this is because many IE workarounds are now hidden behind anisIE check so a support comment mentioning Edge would be confusing as Edge wouldn't execute that code.

IE is quite special here as that's the only browser which we detect as a browser to work around its bugs instead of running support tests.

@mgol
Copy link
MemberAuthor

mgol commentedSep 21, 2020
edited
Loading

Travis fails because tests on Firefox ESR are run on version 68 at the moment. That version doesn't support thenonce property yet as that was onlyfixed in v75. Support for Firefox 68 ESRends tomorrow so I can re-run Travis tomorrow or the day after that.

Comment on lines +7 to +8
return jQuery.contains( elem.ownerDocument, elem ) ||
elem.getRootNode( composed ) === elem.ownerDocument;
Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Reorganizing the definitions decreased the gzipped size a bit.

Also, restrict some workarounds that were applied unconditionally in allbrowsers to run only in IE now. This slightly increases the size but reducesthe performance burden on modern browsers that don't need the workarounds.Also, clean up some comments & remove some obsolete workarounds.Fixesjquerygh-4568
@mgolmgol changed the titleCore: Drop support for EdgeHTML (i.e. non-Chromium Microsoft Edge)Core: Drop support for Edge Legacy (i.e. non-Chromium Microsoft Edge)Sep 22, 2020
@mgolmgol merged commite35fb62 intojquery:masterSep 22, 2020
@mgolmgol deleted the drop-edgehtml branchSeptember 22, 2020 15:49
@mgolmgol added this to the4.0.0 milestoneSep 22, 2020
mgol added a commit to mgol/jquery that referenced this pull requestJun 29, 2023
Both IE & Edge Legacy need the workaround of calling `setDocument()` in an`unload` handler to avoid "permission denied" errors. However, due to not beingpossible to feature-detect this issue, the handler has been applied in allbrowsers for windows different than the one in which jQuery was loaded.jQuery 4.0, which drops Edge Legacy support, guards this workaround witha `document.documentMode` check. This won't work in the 3.x line due to stillsupporting Edge Legacy but we can check for`document.documentElement.msMatchesSelector` instead as that API is supportedin IE 9+ and all Edge Legacy versions.Fixesjquerygh-5281Refjquerygh-4792
mgol added a commit that referenced this pull requestJul 10, 2023
Both IE & Edge Legacy need the workaround of calling `setDocument()` in an`unload` handler to avoid "permission denied" errors. However, due to not beingpossible to feature-detect this issue, the handler has been applied in allbrowsers for windows different than the one in which jQuery was loaded.jQuery 4.0, which drops Edge Legacy support, guards this workaround witha `document.documentMode` check. This won't work in the 3.x line due to stillsupporting Edge Legacy but we can check for`document.documentElement.msMatchesSelector` instead as that API issupported in IE 9+ and all Edge Legacy versions.Fixesgh-5281Closesgh-5282Refgh-4792
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@timmywiltimmywiltimmywil approved these changes

Assignees

@mgolmgol

Milestone
4.0.0
Development

Successfully merging this pull request may close these issues.

Drop support for Edge Legacy (EdgeHTML-based) in 4.0?
2 participants
@mgol@timmywil

[8]ページ先頭

©2009-2025 Movatter.jp