Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.3.0.GA_P02, 4.0
-
Fix Version/s: EE-3.3.0.GA_P03, 4.1
-
Component/s: ICECORE-Components
-
Labels:None
-
Environment:All
-
Assignee Priority:P1
-
Support Case References:Support Case #13325 - https://icesoft.my.salesforce.com/50070000013W5UR
Description
Feature Request: Currently the focusManager for attribute can be set for a component id so that when the page is loaded focus will be set on this component. The request is to investigate to see if it is possible to have focus set when an ajax update occurs (button click, menu selection, etc).
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Re-opened.
My own testing using a modified IF 4 showcase demo page (attached), which adds ace:ajax tags to each of the ace:textEntry inputs, shows a scenario where the focus is being incorrectly set.
To reproduce:
- Run the demo
- Set the selectMenu to set focus on entry "B" (focus is set on B correctly)
- Tab through the entry fields, see the required error correctly appear after tabbing our of entry "D" and "E"
- If you then enter valid data into "E", and then "D", the focus will often incorrectly be set back to "B" once all fields are valid again, instead of to the next entry in the tab-order. I was using shift-tab to go backwards in the tab-order so when focus should have gone to "C", it was going to "B" instead.
Show
Ken Fyten
added a comment - Re-opened.
My own testing using a modified IF 4 showcase demo page (attached), which adds ace:ajax tags to each of the ace:textEntry inputs, shows a scenario where the focus is being incorrectly set.
To reproduce:
Run the demo
Set the selectMenu to set focus on entry "B" (focus is set on B correctly)
Tab through the entry fields, see the required error correctly appear after tabbing our of entry "D" and "E"
If you then enter valid data into "E", and then "D", the focus will often incorrectly be set back to "B" once all fields are valid again, instead of to the next entry in the tab-order. I was using shift-tab to go backwards in the tab-order so when focus should have gone to "C", it was going to "B" instead.
Attached modified focus-manager demo with added ace:ajax calls.
Test application /ICE-10601.jsf was added to:
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Nightly/focusManager
Show
Liana Munroe
added a comment - Test application / ICE-10601 .jsf was added to:
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Nightly/focusManager
Keep track of previously focus components only if they are not focused as a result of invalidity.
Show
Mircea Toma
added a comment - Keep track of previously focus components only if they are not focused as a result of invalidity.
Verified ICEfaces EE-3.3.0.GA_P03 tag, EE-3.3.0 maintenance branch, ICEfaces 4 trunk r44630. Tomcat 7, IE 11, FF 34, Chrome 42.
Show
Liana Munroe
added a comment - Verified ICEfaces EE-3.3.0.GA_P03 tag, EE-3.3.0 maintenance branch, ICEfaces 4 trunk r44630. Tomcat 7, IE 11, FF 34, Chrome 42.
Modified component to apply focus only when the chosen component is different from last focus application to avoid interfering with submits triggered during the 'blur' events. Without this provision the focus will be put back right away as described in issue
ICE-9639.