Improved "Auto Focus" Option Behavior
The "Auto Focus " option currently fails to place the cursor in the first input field when it is the second element in a flow after a list box. This results in a non-intuitive user experience, requiring users to navigate through other elements before reaching the input field. We request an enhancement to ensure the cursor is directly placed in the first input field, or at least the list box, when "Auto Focus Input" is enabled, providing a smoother user experience.
-
Pontus Leander commented
We use Check Boxes so the user can make swift adjustments to whatever the next step is.
One example is flows where we give the user the option to print a label or not when scanning and item.
Note: This is an issue that affects the Web NG-client. In the Android-client, users usually scan, and that works even if we got checkboxes above an input field.
Wen cant put the check boxes after the input field because that would because that will cause the Andorid-client not to press the Default button after a scan.