Skip to content

fix(scrollable-region-focusable): do not fail scroll areas when all content is visible without scrolling#4993

Merged
straker merged 2 commits intodevelopfrom
scrollable-region-visbile
Feb 5, 2026
Merged

fix(scrollable-region-focusable): do not fail scroll areas when all content is visible without scrolling#4993
straker merged 2 commits intodevelopfrom
scrollable-region-visbile

Conversation

@straker
Copy link
Copy Markdown
Contributor

@straker straker commented Jan 23, 2026

Scrollable-region-focusable-matches now tests the text rects or bounding rect of all content to see if is outside the bounding rect of the scroll container. Only then does it pass the matcher.

This changed made many of the integration test cases inapplicable so I moved them to the bottom of the file to be grouped with the other inapplicable results. For the unit tests I had to pad some of the tests with more content in order for the visible content to require scrolling.

Closes: #4535

@straker straker requested a review from a team as a code owner January 23, 2026 17:13
Copy link
Copy Markdown
Contributor

@WilcoFiers WilcoFiers left a comment

Choose a reason for hiding this comment

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

LGTM

@straker straker merged commit 838707a into develop Feb 5, 2026
23 checks passed
@straker straker deleted the scrollable-region-visbile branch February 5, 2026 14:58
WilcoFiers pushed a commit that referenced this pull request Mar 30, 2026
…ontent is visible without scrolling (#4993)

Scrollable-region-focusable-matches now tests the text rects or bounding
rect of all content to see if is outside the bounding rect of the scroll
container. Only then does it pass the matcher.

This changed made many of the integration test cases inapplicable so I
moved them to the bottom of the file to be grouped with the other
inapplicable results. For the unit tests I had to pad some of the tests
with more content in order for the visible content to require scrolling.

Closes: #4535
straker added a commit that referenced this pull request Mar 30, 2026
…ontent is visible without scrolling (#4993)

Scrollable-region-focusable-matches now tests the text rects or bounding
rect of all content to see if is outside the bounding rect of the scroll
container. Only then does it pass the matcher.

This changed made many of the integration test cases inapplicable so I
moved them to the bottom of the file to be grouped with the other
inapplicable results. For the unit tests I had to pad some of the tests
with more content in order for the visible content to require scrolling.

Closes: #4535
@straker straker mentioned this pull request Mar 30, 2026
WilcoFiers added a commit that referenced this pull request Mar 31, 2026
### [4.11.2](v4.11.1...v4.11.2)
(2026-03-30)

### Bug Fixes

- **aria-valid-attr-value:** handle multiple aria-errormessage IDs
([#4973](#4973))
([9322148](9322148))
- **aria:** prevent getOwnedVirtual from returning duplicate nodes
([#4987](#4987))
([99d1e77](99d1e77)),
closes [#4840](#4840)
- **DqElement:** avoid calling constructors with cloneNode
([#5013](#5013))
([88bc57f](88bc57f))
- **existing-rule:** aria-busy now shows an error message for a use with
unallowed children
([#5017](#5017))
([dded75a](dded75a))
- **scrollable-region-focusable:** clarify the issue is in safari
([#4995](#4995))
([2567afd](2567afd)),
closes
[WebKit#190870](https://github.com/dequelabs/WebKit/issues/190870)
[WebKit#277290](https://github.com/dequelabs/WebKit/issues/277290)
- **scrollable-region-focusable:** do not fail scroll areas when all
content is visible without scrolling
([#4993](#4993))
([240f8b5](240f8b5))
- **target-size:** determine offset using clientRects if target is
display:inline
([#5012](#5012))
([69d81c1](69d81c1))
- **target-size:** ignore widgets that are inline with other inline
elements ([#5000](#5000))
([cf8a3c0](cf8a3c0))
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.

scrollable-region-focusable should consider an element's content real content, not its content box

2 participants