-
Notifications
You must be signed in to change notification settings - Fork 715
Starting point isn't changed when searching outside of a container #3358
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
Comments
Migrated from WICG/spatial-navigation#128 (comment) Oh, I see. Then I can see two topics here: [Topic 1] Topic 1 is also related to WICG/spatial-navigation#129. But for Topic 2, why do you think that the scope for searching the candidate is the visual bounding box only when the focus moving outside? |
Migrated from WICG/spatial-navigation#128 (comment)
Look at @junhoseo's test case. It demonstrates why we cannot use the scroll container's edge when searching outside of the [focused] scroll container.
Spatnav should never move focus to an offscreen element... When moving towards a scroll container, no matter if it contains visible focusables or not, focus should first go to the scroll container itself. (Remember that scroll containers are focusables too.) |
Migrated from WICG/spatial-navigation#128 (comment)
Yes, that's what I mean, but this is only when searching outside the scroll container. |
Migrated from WICG/spatial-navigation#128 (comment) In current spec, the focus moves inside or outside of the scrollable element depending on the bounding border box of the scrollable element. I'm not sure I understand clearly about your point.
|
The issue migration script created some duplicates. #3392 is the same as this one. |
Migrated from WICG/spatial-navigation#128
Originally created by @hugoholgersson on Thu, 01 Nov 2018 20:33:20 GMT
I created a Chromium-bug that describes this in problem in more detail: https://crbug.com/900499.
The current algorithm (pictured in 7.2) does not change the starting point* when climbing to an ancestor container.
* In Chrome we use the term "search origin" instead of "starting point".
The text was updated successfully, but these errors were encountered: