Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Beta1
-
Fix Version/s: 2.0.0
-
Component/s: ICE-Components
-
Labels:None
-
Environment:ICEfaces 2.0
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration
Description
Typical ICEfaces 2.0 applications will contain pages with a mixture of h: component with singleSubmit and compat components. The expected behavior from the page developer's point of view will be that the compat components also support singleSubmit. For instance, singleSubmit does not run validators for non-submitting components, whereas partialSubmit does.
The expectation is that users will either use "partialSubmit" if they have an existing code-base written to use it, or else they would use "singleSubmit" tag instead. Using both at the same time is not supported.
The first task for this is to develop test cases that will indicate the current level of support within the compat components for singleSubmit. Basically, a set of pages that use each compat component inside a form with a "singleSubmit=true" tag, and partialSubmit=false on each component.
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | Ken Fyten [ ken.fyten ] |
Salesforce Case | [] | |
Fix Version/s | 2.0.0 [ 10230 ] |
Salesforce Case | [] | |
Affects | [Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration] | |
Assignee Priority | P1 |
Salesforce Case | [] | |
Description |
Typical ICEfaces 2.0 applications will contain pages with a mixture of h: component with singleSubmit and compat components. The expected behavior from the page developer's point of view will be that the compat components also support singleSubmit. For instance, singleSubmit does not run validators for non-submitting components, whereas partialSubmit does. |
Typical ICEfaces 2.0 applications will contain pages with a mixture of h: component with singleSubmit and compat components. The expected behavior from the page developer's point of view will be that the compat components also support singleSubmit. For instance, singleSubmit does not run validators for non-submitting components, whereas partialSubmit does. The expectation is that users will either use "partialSubmit" if they have an existing code-base written to use it, or else they would use "singleSubmit" tag instead. Using both at the same time is not supported. The first task for this is to develop test cases that will indicate the current level of support within the compat components for singleSubmit. Basically, a set of pages that use each compat component inside a form with a "singleSubmit=true" tag, and partialSubmit=false on each component. |
Salesforce Case | [] | |
Affects | [Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration] | [Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration] |
Description |
Typical ICEfaces 2.0 applications will contain pages with a mixture of h: component with singleSubmit and compat components. The expected behavior from the page developer's point of view will be that the compat components also support singleSubmit. For instance, singleSubmit does not run validators for non-submitting components, whereas partialSubmit does. The expectation is that users will either use "partialSubmit" if they have an existing code-base written to use it, or else they would use "singleSubmit" tag instead. Using both at the same time is not supported. The first task for this is to develop test cases that will indicate the current level of support within the compat components for singleSubmit. Basically, a set of pages that use each compat component inside a form with a "singleSubmit=true" tag, and partialSubmit=false on each component. |
Typical ICEfaces 2.0 applications will contain pages with a mixture of h: component with singleSubmit and compat components. The expected behavior from the page developer's point of view will be that the compat components also support singleSubmit. For instance, singleSubmit does not run validators for non-submitting components, whereas partialSubmit does. The expectation is that users will either use "partialSubmit" if they have an existing code-base written to use it, or else they would use "singleSubmit" tag instead. Using both at the same time is not supported. The first task for this is to develop test cases that will indicate the current level of support within the compat components for singleSubmit. Basically, a set of pages that use each compat component inside a form with a "singleSubmit=true" tag, and partialSubmit=false on each component. |
Assignee | Ken Fyten [ ken.fyten ] | Nils Lundquist [ nils.lundquist ] |
Salesforce Case | [] | |
Assignee | Nils Lundquist [ nils.lundquist ] | Ted Goddard [ ted.goddard ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #23245 | Tue Nov 30 09:54:52 MST 2010 | ted.goddard | ice:loadBundle is incompatible with partial rendering, so replaced with f:loadBundle ( |
Files Changed | ||||
![]() |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #23246 | Tue Nov 30 09:55:46 MST 2010 | ted.goddard | removed ace from this branch due to build problems ( |
Files Changed | ||||
![]() |
Assignee | Ted Goddard [ ted.goddard ] | Mandeep Hayher [ mandeep.hayher ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #23281 | Thu Dec 02 13:38:31 MST 2010 | ted.goddard | using onclick for select components ( |
Files Changed | ||||
![]() |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #23282 | Thu Dec 02 13:39:01 MST 2010 | ted.goddard | using onclick for select components ( |
Files Changed | ||||
![]() |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #23284 | Thu Dec 02 15:54:54 MST 2010 | ted.goddard | detecting simulated onchange in select ( |
Files Changed | ||||
![]() |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #23285 | Thu Dec 02 15:59:41 MST 2010 | ted.goddard | detecting simulated onchange in select ( |
Files Changed | ||||
![]() |
Status | Open [ 1 ] | Resolved [ 5 ] |
Assignee Priority | P1 | |
Resolution | Fixed [ 1 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Since we already have the compat/samples/component-showcase application, including automated Selenium test scripts, it would be a good place to start. This sample needs to be modified to use the <icecore:singleSubmit> tag inside each form for each component demo, and also to remove the use of any "partialSubmit=true" attributes on any forms or other ice:components in the sample application. Observing the submit behavior of each component demo after this change is made will give us a reasonable initial indication of whether or not the component is behaving as expected.