-
Bug
-
Resolution: Obsolete
-
Neutral
-
None
-
5.4.1
The tab order in modal dialogs is currently problematic once you're tabbing beyond the first or last element of the dialog. The browser then switches to another element in the UI, which is confusing, since it's supposed to stay inside the modal dialog.
The tab order should remain inside a modal dialog. For embedded forms, it can go beyond that.
Christopher has already done some research on this. It seems that it's not easy to constrain the tab order inside a closed set of elements without "manual" intervention using JS. Two options we shortly touched in a discussion was to have listeners on the first and the last element in a dialog that react once a user wants to tab beyond the dialog; or to remove or otherwise disable the "tabindex" HTML attribute for all UI elements, which are currently not part of a modal dialog.
- depends upon
-
MGNLUI-2876 Form Tabs should be part of the focus order in a dialog - and should be triggerable via keyboard.
- Closed
-
MGNLDAM-440 Change FilePreviewComponent and DamUploadField to use CssLayout instead of AbsoluteLayout
- Closed
- duplicates
-
MGNLUI-2619 Tabbing must be scoped to current dialog
- Closed
-
MGNLUI-321 Dialogs: fix focus order and put focus on a default field
- Closed
-
MGNLUI-1781 Dialogs should ensure the Tab key is "captured"
- Closed
- relates to
-
MGNLUI-2673 Support of ESC and ENTER in dialogs, detail editors, alerts and notifications
- Closed