Hi, I have a question about keyboard navigation with the Tab key.
In our UI we have a set of input fields where the code (components, order, and focus configuration) is the same, but the ability to move between fields using the Tab key is inconsistent: sometimes Tab moves focus correctly to the next field, other times it doesn’t, without any change in the code.
Could you help me understand what could cause this inconsistent Tab behavior (e.g. known bugs, focus/TabIndex issues, browser differences, or something related to Vaadin version 25), and what is the recommended way to debug or ensure stable keyboard navigation between fields?
I am not sure what you mean by inconsistent. It would help us to understand if you would present more detailed specific example and explain what you expect to that happen there and how the actual behavior differs from what you expect.
Are you now referring to the same UI / form behaving differently from time to time, or similar UIs / forms behaving differently due some minimal difference in them?
Vaadin does not manage focus order in any way – it just relies on the native html principle that the order in which focusable elements occur in the DOM is the order in which they get focused when tabbing. (The exception to the rule is shadow DOM where the order of slots in which light-DOM elements are placed determine the focus order, rather than the order of the slotted elements in the DOM, but that’s still just native html focusing).
Are you by any chance using setTabIndex on those fields?
