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.

Sign up for GitHub

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

Jump to bottom

Clarify behaviour in case of overlaps/overlays #36

Merged
merged 3 commits into from
Jan 22, 2024
Merged

Clarify behaviour in case of overlaps/overlays #36

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
68b2aa1
Clarify behaviour in case of overlaps/overlays
ShiningTrapez Jan 3, 2024
dccfc3f
Merge branch 'master' into overlap-readme-update
ShiningTrapez Jan 17, 2024
d47127b
Merge branch 'master' into overlap-readme-update
Murreey Jan 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,8 @@ By default, LRUD will measure to all candidates that are in the direction to mov

This threshold can be adjusted on a per-element basis with the `data-lrud-overlap-threshold` attribute, as a float from 0.0 to 1.0. An overlap of 0.0 will make a candidate only be considered if it is located _entirely_ in the direction of movement.

Please also note that LRUD does not consider the Z Axis, which can cause surprising results with elements that are overlapped in this way, including in the case of full screen overlays on existing UIs. The above attribute can help alleviate this issue.

## Containers

Focusables can be wrapped in containers. Containers can keep track of the last
Expand Down
Loading