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
When working with a few nodes that have multiple input values, we have to click in each input to modify them one by one and TAB key doesn't work. This can get tiresome, and can frustrate users who need such accessibility features.
Expected behavior:
I have a graph with multiple connected nodes, each node having a few input fields (text, number, dropdowns…)
I select one input and fill it.
I press the TAB key to go to the next input
The next input in the list (next selectable element in the DOM or according to tabindex) is focused and the graph translated to center to the next input element if needed.
I press Shift + TAB key to go to the previous input
The previous input in the list (previous selectable element in the DOM or according to tabindex) is focused and the graph translated to the next input element if needed.
Current behavior
I have a graph with multiple connected nodes, each node having a few input fields (text, number, dropdowns…)
When not disabling the key, using the tab key indeed goes to the next input element but the window will automatically scroll to the focused element (instead of translating the background and the graph) and will break the layout.
I managed to hack around the issue by redefining the keyDown function and re-writing the "focus to the next/previous element" to manually focus() with preventScroll option to true, so user can still use the tab key but it won't scroll to the element.
Sorry for eventual english mistakes, let me know if any information is missing :)
Have a nice day!
The text was updated successfully, but these errors were encountered:
When working with a few nodes that have multiple input values, we have to click in each input to modify them one by one and TAB key doesn't work. This can get tiresome, and can frustrate users who need such accessibility features.
Expected behavior:
Current behavior
Additional details
keyDown
function and re-writing the "focus to the next/previous element" to manuallyfocus()
withpreventScroll
option to true, so user can still use the tab key but it won't scroll to the element.Sorry for eventual english mistakes, let me know if any information is missing :)
Have a nice day!
The text was updated successfully, but these errors were encountered: