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

test: fix aria tests in Firefox Nightly #3792

Merged
merged 4 commits into from
Oct 12, 2023

Conversation

nolanlawson
Copy link
Contributor

Details

Firefox 119 (scheduled to be released on October 24th) will potentially contain a bug that will break a bunch of our ARIA reflection tests. Rather than wait to be broken, let's proactively make these tests resilient to Firefox 119.

Note that I didn't bother to add Firefox Nightly to our test matrix, because I don't think it's worth it to run in CI every time. So you'll have to believe me that these new tests pass. πŸ™ƒ

Does this pull request introduce a breaking change?

  • βœ… No, it does not introduce a breaking change.

Does this pull request introduce an observable change?

  • βœ… No, it does not introduce an observable change.

@nolanlawson nolanlawson requested a review from a team as a code owner October 11, 2023 23:10
// Our polyfill or the current spec – setting undefined is not treated like null
// Our polyfill - null removes
falsyValuesThatRemove.push(null);
// Our polyfill – setting undefined is not treated like null
falsyValuesThatDoNotRemove.push(undefined);
}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

A lot of these tests are kind of dumb – testing a thing, and then asserting that your test does the same thing it just did. Maybe once the browsers are all in alignment, we can vastly simplify this test.

Copy link
Member

@jmsjtu jmsjtu left a comment

Choose a reason for hiding this comment

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

Verified with Firefox Nightly 120.0a1 and tests are passing!

Side note, do you think we should add safari + firefox karma launchers to the integration-karma repos? (Doesn't look like they've been updated in a while though)

I'm thinking about having the dev dependencies installed but not configured to run by default for local setups, might help reduce setting it up for local testing.

@nolanlawson
Copy link
Contributor Author

I don't personally think it's worth it – it's an extra dependency, and right now I find that karma start plus opening the URL in another browser works pretty well. Plus it's the only way I can think of to test exotic browsers like Firefox Nightly, Safari Technology Preview, etc.

@nolanlawson nolanlawson merged commit b37a31e into master Oct 12, 2023
11 checks passed
@nolanlawson nolanlawson deleted the nolan/proactively-fix-firefox branch October 12, 2023 16:08
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.

None yet

2 participants