Move focus around a HTML document using Left, Right, Up, Down keys.
getNextFocus(currentFocus, keyOrKeyCode, [scope])
currentFocus
should be anHTMLElement
that you want LRUD spatial to consider as the element you are navigating from. In simple applications, this can just be a reference todocument.activeElement
.keyOrKeyCode
should be akey
string or akeyCode
decimal representing the directional key pressed.scope
is an optionalHTMLElement
that you only want to look for focusable candidates inside of. Defaults to the whole page if not provided.
An HTMLElement
that LRUD spatial thinks you should
navigate to.
LRUD spatial defines focusable elements as those which match any of the following CSS selectors:
[tabindex]
a
button
input
Any potential candidate with the lrud-ignore
class, or inside any parent with the lrud-ignore
class, will not be considered focusable and will be skipped over. By default LRUD will not ignore candidates that have opacity: 0
or have a parent with opacity: 0
, so this class can be used for that.
By default, LRUD will measure to all candidates that are in the direction to move. It will also include candidates that overlap the current focus by up to 30%, allowing for e.g. a 'right' movement to include something that is above the current focus, but has half of it's size expanding to the right.
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.
Focusables can be wrapped in containers. Containers can keep track of the last
active focusable item within them using a data-focus
attribute.
Focusables that should be tracked must have a unique ID attribute.
When a container has no previous focus state, it's first focusable element is used instead.
At this time, containers are defined as matching the CSS selectors:
nav
, section
or .lrud-container
.
Adding attribute data-lrud-consider-container-distance
on a container will make LRUD also measure distances to that container's boundary, as well as its children. If the container is the closest of all the possible candidates assessed, LRUD will return one of its children - even if they are not necessarily the spatially closest focusable. The above container focus logic will still be used, so if the container has a previous focus state that will be the returned element. This allows for layouts where moving between containers is the desired behaviour, but their individual elements may not be in the correct positions for that. By default LRUD will only consider focusables when measuring, and ignores container positions.
In some instances, it is desirable to prevent lrud-spatial from selecting another
"best candidate" for example at the bottom of a list. To do this, a container element
should add an additional data-block-exit
attribute to prevent further selection in
that direction. This should be a space separated list.
E.g.
<div class="lrud-container" data-block-exit="up down">...</div>
To determine the next element that should be focused;
- Uses the key code to get the direction of movement
- From the currently focused DOM element, get the coordinates of the edge corresponding to the direction you are moving
- For all other focusable elements, get the coordinates of the opposite edge (the edge you are entering)
- Find the line between the exit and entry coordinates that has the shortest length
Requirements: Node.js 18
To get started, run npm ci
.
npm run build
will emit a transpiled and minified version of the library.
This is run during CI to prepare the artifact published to NPM. It can also be
useful for integrating against another local project with npm link
.
The test/layouts
directory contains HTML designed to mirror various
real-world use cases, and allow for behavioural vertification of library
features such as containers and grids.
Significant new features should come with corresponding layouts that test them.
Use npm test
to run the tests.
The tests use puppeteer to spin up a
headless browser. The browser loads the layouts mentioned above and runs
scenarios from lrud.test.js against the unminified
code from lib/
.
To investigate why a test is failing, or just to hack on some changes... run
npm run server
. Then go to http://localhost:3005 and
select a layout.
TVOpenSource@bbc.co.uk - we aim to respond to emails within a week.