Skip to content
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

feat: Deprecated Internet Explorer support #3644

Merged
merged 3 commits into from
Sep 8, 2022
Merged

Conversation

WilcoFiers
Copy link
Contributor

As of axe-core 4.5, Internet Explorer 11 is deprecated. Support will be fully dropped with the release of axe-core 5.0, which will come at least 6 months after the 5.0 release to give sufficient time to upgrade.

As of this pull request, we will no longer run automated tests on Internet Explorer. Any bugs reported against IE11 will be investigated and addressed, and the axe-core team will continue to keep limitations imposed by Internet Explorer in mind.

Closes issue: #3534

@WilcoFiers WilcoFiers requested a review from a team as a code owner September 7, 2022 09:31
straker
straker previously requested changes Sep 7, 2022
@@ -52,18 +52,6 @@ jobs:
key: v9-cache-unix-{{ checksum "package-lock.json" }}
Copy link
Contributor

Choose a reason for hiding this comment

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

There's also the orbs: win, restore_dependency_cache_win, and win_box steps that can be removed

'<span id="shadowTarget" style="color: #ccc;">Text</span>' +
'</div>';
axe.testUtils.flatTreeSetup(fixture);
(shadowSupported ? it : xit)(
Copy link
Contributor

@straker straker Sep 7, 2022

Choose a reason for hiding this comment

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

With IE11 gone all our tests run in browsers that support shadow dom (Chrome and Firefox). We should get rid of shadowSupported as well (I'm fine if it's a separate pr / tech debt ticket).

@@ -429,23 +426,17 @@ describe('preload cssom integration test', function() {
commonTestsForRootNodeAndNestedFrame();
});

describe('tests for nested document', function() {
before(function() {
if (!nestedFrame || isIE11) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a chance that nestedFrame will ever be false that we need the if statement still?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have no idea why this was ever there. It wasn't necessary. (otherwise the tests would have failed)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants