Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Won't Fix
-
Affects Version/s: EE-3.3.0.GA_P02, 4.0
-
Fix Version/s: EE-3.3.0.GA_P03, 4.1
-
Component/s: Framework, ICECORE-Components
-
Labels:None
-
Environment:All
-
Assignee Priority:P1
-
Support Case References:Support Case #13325 - https://icesoft.my.salesforce.com/50070000013W5UR
-
Workaround Exists:Yes
-
Workaround Description:If possible, turn off the IECfaces focus retention with the icecore:config focusManaged=false tag.
Description
A call to ice.applyFocus is being overridden by the ICEfaces focus retention. The call is used as follows and is trying to set focus to an input that is already in the form:
<ice:commandButton id="clearBtn" value="Clear"
actionListener="#{testBean.clear}"
onclick="ice.applyFocus('iceForm:inputOne');"/>
<ice:commandButton id="clearBtn" value="Clear"
actionListener="#{testBean.clear}"
onclick="ice.applyFocus('iceForm:inputOne');"/>
Activity
Arran Mccullough
created issue -
Arran Mccullough
made changes -
Field | Original Value | New Value |
---|---|---|
Affects Version/s | 4.0 [ 11382 ] |
Arran Mccullough
made changes -
Attachment | Case13325Example.war [ 18587 ] | |
Attachment | Case13325Example.zip [ 18588 ] |
Ken Fyten
made changes -
Assignee | Ken Fyten [ ken.fyten ] |
Ken Fyten
made changes -
Fix Version/s | 4.1 [ 11375 ] | |
Fix Version/s | EE-3.3.0.GA_P03 [ 11572 ] |
Ken Fyten
made changes -
Assignee | Ken Fyten [ ken.fyten ] | Mircea Toma [ mircea.toma ] |
Ken Fyten
made changes -
Assignee Priority | P1 [ 10010 ] |
Mircea Toma
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Won't Fix [ 2 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
I've tested this with ICEfaces 4.x as well using the standard JSF components. The same issue is seen here where focus is lost once the update is applied.
I also tested with the <icecore:focusManager/> tag. This didn't change the behavior when having it set for the ID of the first input field: <icecore:focusManager for="inputOne">. With the Showcase demo of this component I can see similar behavior: