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
Activity
Ken Fyten
created issue -
Ken Fyten
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Mircea Toma [ mircea.toma ] | |
Fix Version/s | 4.0 [ 11382 ] | |
Affects | Documentation (User Guide, Ref. Guide, etc.),Sample App./Tutorial [ 10003, 10001 ] | |
Assignee Priority | P3 [ 10012 ] |
Ken Fyten
made changes -
Fix Version/s | EE-3.3.0.GA_P02 [ 11371 ] |
Ken Fyten
made changes -
Workaround Description | A potential workaround for this is to use the new ice core:focusManager component on the page, and have the application programmatically set the focus to the desired field inside the ace:dialog when it is shown via "visible=true", by specifying the id of the component to receive focus in the focusManager's "for" attribute. | |
Workaround Exists | Yes [ 10007 ] |
Ken Fyten
made changes -
Workaround Description | A potential workaround for this is to use the new ice core:focusManager component on the page, and have the application programmatically set the focus to the desired field inside the ace:dialog when it is shown via "visible=true", by specifying the id of the component to receive focus in the focusManager's "for" attribute. | A potential workaround for this is to use the new icecore:focusManager component on the page, and have the application programmatically set the focus to the desired field inside the ace:dialog when it is shown via "visible=true", by specifying the id of the component to receive focus in the focusManager's "for" attribute. |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #40815 | Tue Apr 15 14:27:57 MDT 2014 | mircea.toma | |
Files Changed | ||||
MODIFY
/icefaces4/trunk/icefaces/ace/component/src/org/icefaces/ace/component/dialog/DialogRenderer.java
MODIFY /icefaces4/trunk/icefaces/ace/component/src/org/icefaces/ace/component/dialog/DialogMeta.java MODIFY /icefaces4/trunk/icefaces/ace/component/resources/icefaces.ace/dialog/dialog.js |
Mircea Toma
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Carmen Cristurean
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #40910 | Thu May 01 14:12:10 MDT 2014 | mircea.toma | |
Files Changed | ||||
MODIFY
/icefaces4/trunk/icefaces/ace/component/resources/icefaces.ace/dialog/dialog.js
|
Ken Fyten
made changes -
Assignee | Mircea Toma [ mircea.toma ] | Ken Fyten [ ken.fyten ] |
Ken Fyten
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
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.