Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: EE-3.3.0.GA_P02, 4.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 4.x
-
Assignee Priority:P3
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial
-
Workaround Exists:Yes
-
Workaround Description:
Description
It would be a nice feature if the ace:dialog supported a new "setFocus" attribute that could be set to define the id of a component contained within the ace:dialog that should receive focus whenever the dialog is made visible, either via the the visible attribute or JavaScript API.
This would provide an easy mechanism for applications to have focus be moved to a component inside the dialog when it is presented. Currently, focus is generally persisted on the component that triggers the dialog being made visible, which is usually not the desired outcome.
This would provide an easy mechanism for applications to have focus be moved to a component inside the dialog when it is presented. Currently, focus is generally persisted on the component that triggers the dialog being made visible, which is usually not the desired outcome.
Issue Links
- blocks
-
ICE-9907 ace:dialog - Focus is not set to first input on opening of dialog
- Closed
Added a workaround based on the new ice core:focusManager technique. However, this workaround would only potentially work with cases where the dialog is being displayed via the server-side "visible" attribute being set to true, and would not support the client-side use-case where the dialog has already been rendered and is being displayed via JavaScript.
For the client-side scenario, having the "setFocus" attribute on the ace:dialog would be handy as it could be pre-rendered with the correct value, and that field would automatically receive focus whenever the dialog was displayed, regardless of whether that was via "visible=true" or the client-side JavaScript API.