-
Notifications
You must be signed in to change notification settings - Fork 36
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
feat(Mover): Connected Movers. #395
base: master
Are you sure you want to change the base?
Conversation
groupper: {}, | ||
mover: { | ||
direction: MoverDirections.Vertical, | ||
connected: MoverConnections.Parent, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are Child
and Parent
relationships both needed for connected movers? Is there a scenario where you can have a parent mover with Child
and only a subset of movers will use Parent
?
</div> | ||
|
||
<div | ||
tabIndex={0} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what happens when a connected mover is not focusable?
}, | ||
})} | ||
> | ||
<button>Button1</button> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update button names to be a bit more specific to their level of nesting
i.e. Button1L3
<div | ||
{...getTabsterAttribute({ | ||
mover: { | ||
direction: MoverDirections.Horizontal, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what happens when parent and child movers share the same direction?
The ability to connect nested Movers via DOM hierarchy so that the parent Movers can continue handling the key press when the child Mover couldn't find new focus target.