Improve Responsive Design accessibility - #60
Draft
issackjohn wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Improve the Responsive Design benchmark's accessibility while keeping its existing layout and workload intact.
Validation
Performance
Crossbench Speedometer 3
Responsive-Design, 10 runs x 10 iterations:Both intervals include zero, so neither browser shows a measurable regression. All Chrome and Edge runs completed without failures.
Safari 26.6 could not produce a final comparison because SafariDriver exited during both the patched run and an immediate unchanged-base smoke run, indicating an automation-environment failure rather than a code-specific result.
This fork-only stacked PR targets
track-carousel-resize-events, so main-only CI does not run here.