-
Notifications
You must be signed in to change notification settings - Fork 6.8k
ci: update remote browsers we test against #19961
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
ci: update remote browsers we test against #19961
Conversation
Updates our remote browsers so that we test against the latest Egde version, the latest iOS and macOS Safari versions.
e000b3e
to
9a56b0d
Compare
…ctly for videos, audio and object elements The interactivity checker has been built a while ago when supported browsers behaved differently for their `tabbable` state. We now updated our browsers to more recent versions, and need to adjust the interactivity checker so that it reflects the latest patterns in supported browsers. Here is a note summary of behavior noticed for `video` and `audio` elements in various supported browsers: https://hackmd.io/@devversion/rkxzcgsJD Another change was for `object` elements. In previous BLINK / Webkit browsers, such elements, or its children were never tabbable. This is incorrect for the currently supported browsers as children inside `object` elements can certainly be tabbable. On the other hand though, object elements itself can be tabbable depending on configuration we cannot reliably detect. For improved accessibility, we never consider object elements itself as tabbable (similar to iframes)
* Updates the MDC-based slider tests to work in Safari v13.1 * Updates the MDC-based slider tests so that the measurements are guaranteed to be based on a 100px wide slider (seems like this is not always the case sometimes; resulting in flakiness).
Note that there is a second PR for updating Firefox. That one is managed by Bazel so it's more complicated. I'm working on a version of Firefox we can control in: angular/angular#38029 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Uh oh!
There was an error while loading. Please reload this page.