You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is any possibility to get next sibling's focus key after press arrow button, but not perform this arrow action ?
Have faced this in realizing smooth ScrollView with active focusable elements inside.
I have a long text with a quite few active controls , and a client should have ability to read FULL text between focusable controls. Standard approach is not good as it changes scroll position to make focused element visible in Viewport, ignoring long not focusable content in-between focusable controls.
The idea is:
On arrow event make predication on desired direction (up/down/left right) ( get next element focusKey and FocusableComponentLayout ), but not performing arrow action mentioned
If next closest focusable element completely stay in Viewport, have to focus on it manually.
Else cases - have to scroll content to fixed distance, i.e. 200 px till next active focusable element appears completely in the view port.
Probably it is a wrong approach, any ideas welcome
Is any possibility to get next sibling's focus key after press arrow button, but not perform this arrow action ?
Have faced this in realizing smooth ScrollView with active focusable elements inside.
I have a long text with a quite few active controls , and a client should have ability to read FULL text between focusable controls. Standard approach is not good as it changes scroll position to make focused element visible in Viewport, ignoring long not focusable content in-between focusable controls.
The idea is:
On arrow event make predication on desired direction (up/down/left right) ( get next element focusKey and FocusableComponentLayout ), but not performing arrow action mentioned
If next closest focusable element completely stay in Viewport, have to focus on it manually.
Else cases - have to scroll content to fixed distance, i.e. 200 px till next active focusable element appears completely in the view port.
Probably it is a wrong approach, any ideas welcome
UPD: related to #117 (comment)
The text was updated successfully, but these errors were encountered: