Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Won't Fix
-
Affects Version/s: 3.2, EE-3.2.0.BETA
-
Fix Version/s: 3.3
-
Component/s: Bridge, ICE-Components
-
Labels:None
-
Environment:IE9 Compat, IE8, IE7
-
Assignee Priority:P2
-
Salesforce Case Reference:
-
Workaround Exists:Yes
-
Workaround Description:
Description
The <icecore:singleSubmit> tag is used on a form. This form contains an ice:selectRadioButton with a "Yes" and a "No" option. The "No" option is selected by default. Sample code:
<ice:selectOneRadio id="testRadio"
value="#{testBean.value}" required="true">
<f:selectItem itemValue="YES" itemLabel="Yes" />
<f:selectItem itemValue="NO" itemLabel="No" />
</ice:selectOneRadio>
When tabbing through this component, the selection is lost and the required message is shown. The setter for the value does not get called. Once another singleSubmit occurs the value is shown again.
This seems to happen on the initial load of the page. If focus is cycled through again this issue isn't seen. Also if the default value is set to "Yes" or the order of the SelectItems is changed then this issue isn't seen.
It also is an issue with the h:selectOneRadio button. This issue is likely related to the behavior reported inICE-8577
<ice:selectOneRadio id="testRadio"
value="#{testBean.value}" required="true">
<f:selectItem itemValue="YES" itemLabel="Yes" />
<f:selectItem itemValue="NO" itemLabel="No" />
</ice:selectOneRadio>
When tabbing through this component, the selection is lost and the required message is shown. The setter for the value does not get called. Once another singleSubmit occurs the value is shown again.
This seems to happen on the initial load of the page. If focus is cycled through again this issue isn't seen. Also if the default value is set to "Yes" or the order of the SelectItems is changed then this issue isn't seen.
It also is an issue with the h:selectOneRadio button. This issue is likely related to the behavior reported in
Issue Links
- duplicates
-
ICE-8577 focus is lost on the form on the first update
- Closed
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Arran Mccullough
created issue -
Arran Mccullough
made changes -
Field | Original Value | New Value |
---|---|---|
Attachment | Case11909Example.zip [ 15368 ] | |
Attachment | Case11909ExampleWAR.zip [ 15369 ] |
Arran Mccullough
made changes -
Salesforce Case Reference | 5007000000QZ05EAAT |
Ken Fyten
made changes -
Assignee | Mircea Toma [ mircea.toma ] | |
Fix Version/s | 3.3 [ 10370 ] | |
Assignee Priority | P2 [ 10011 ] |
Mircea Toma
made changes -
Mircea Toma
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Won't Fix [ 2 ] |
Mircea Toma
made changes -
Workaround Description |
Set the default value to "YES" or change the order of the selectItems:
<f:selectItem itemValue="NO" itemLabel="No" /> <f:selectItem itemValue="YES" itemLabel="Yes" /> |
Most often the workaround for this issue is to setup a index.jsp page that redirects to the main JSF page of the application. This way by the time the main JSF page is accessed the session tracking cookie is set, thus JSF will not render jsessionid path parameters into the form URLs.
Another workaround is to use org.icefaces.diffConfig=att context parameter to enable attribute updates, this will target the form[action] attribute modifications. |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |