Details
-
Type: New Feature
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.1
-
Component/s: ACE-Components, MOBI-Components
-
Labels:None
-
Environment:ICEfaces 4
-
Assignee Priority:P2
-
ICEsoft Forum Reference:
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
Description
A useful feature for an application is to provide a "Reset" button on a form to allow the use to reset all form fields to their original states, prior to any user modifications.
Historically, the HTML input type="reset" was used for this function (e.g. " <input type="reset" value="Reset!">"). However, with the more advanced and complex components provided by ACE and MOBI, the basic form-field reset capability provided by the HTML input technique is no longer sufficient to ensure proper value resetting.
While, the native reset button not only clears input elements but also resets those elements to the values with which they were loaded initially, in the case of our components the notion of an original value is not straight-forward, since our components' values can be programmatically updated, and also ajax requests can save components' values multiple times in a user session. This makes it unclear to determine what really are the original components' values.
This JIRA is to investigate and ultimately provide an easy to use mechanism for clearing all components in a form reliably, whether they be ACE, MOBI, or "h:" / standard JSF components.
Note that this JIRA would likely provide a JavaScript-based mechanism for clearing the components in a form, but ultimately this JS function would be integrated into a new "clear" mode for the existing ace:pushButton component (under a separate JIRA -ICE-10115).
Historically, the HTML input type="reset" was used for this function (e.g. " <input type="reset" value="Reset!">"). However, with the more advanced and complex components provided by ACE and MOBI, the basic form-field reset capability provided by the HTML input technique is no longer sufficient to ensure proper value resetting.
While, the native reset button not only clears input elements but also resets those elements to the values with which they were loaded initially, in the case of our components the notion of an original value is not straight-forward, since our components' values can be programmatically updated, and also ajax requests can save components' values multiple times in a user session. This makes it unclear to determine what really are the original components' values.
This JIRA is to investigate and ultimately provide an easy to use mechanism for clearing all components in a form reliably, whether they be ACE, MOBI, or "h:" / standard JSF components.
Note that this JIRA would likely provide a JavaScript-based mechanism for clearing the components in a form, but ultimately this JS function would be integrated into a new "clear" mode for the existing ace:pushButton component (under a separate JIRA -
Issue Links
- blocks
-
ICE-10912 ace:selectMenu, inField label is not restored when clearing the component
- Closed
-
ICE-9501 ACE javascript components reseting when reset button pressed
- Closed
-
ICE-10898 Add "Reset" capability to ACE, MOBI components
- Closed
-
ICE-10115 Add a new "clear" mode to the ace:pushButton, ace:linkButton
- Closed
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Ken Fyten
created issue -
Ken Fyten
made changes -
Field | Original Value | New Value |
---|---|---|
Description |
A useful feature for an application is to provide a "Reset" button on a form to allow the use to reset all form fields to their original states, prior to any user modifications.
Historically, the HTML input type="reset" was used for this function (e.g. " <input type="reset" value="Reset!">"). However, with the more advanced and complex components provided by ACE and MOBI, the basic form-field reset capability provided by the HTML input technique is no longer sufficient to ensure proper value resetting. This JIRA is to investigate and ultimately provide an easy to use mechanism for resetting all components in a form reliably, whether they be ACE, MOBI, or "h:" / standard JSF components. Note that this JIRA would likely provide a JavaScript-based mechanism for resetting the components in a form, but ultimately this JS function would be integrated into a new "reset" type for the existing ace:pushButton component (under a separate JIRA). |
A useful feature for an application is to provide a "Reset" button on a form to allow the use to reset all form fields to their original states, prior to any user modifications.
Historically, the HTML input type="reset" was used for this function (e.g. " <input type="reset" value="Reset!">"). However, with the more advanced and complex components provided by ACE and MOBI, the basic form-field reset capability provided by the HTML input technique is no longer sufficient to ensure proper value resetting. This JIRA is to investigate and ultimately provide an easy to use mechanism for resetting all components in a form reliably, whether they be ACE, MOBI, or "h:" / standard JSF components. Note that this JIRA would likely provide a JavaScript-based mechanism for resetting the components in a form, but ultimately this JS function would be integrated into a new "reset" type for the existing ace:pushButton component (under a separate JIRA - |
Ken Fyten
made changes -
Fix Version/s | 4.1 [ 11375 ] |
Ken Fyten
made changes -
Assignee | Mircea Toma [ mircea.toma ] | |
Assignee Priority | P2 [ 10011 ] |
Ken Fyten
made changes -
Assignee | Mircea Toma [ mircea.toma ] | Ken Fyten [ ken.fyten ] |
Ken Fyten
made changes -
Assignee | Ken Fyten [ ken.fyten ] | Arturo Zambrano [ artzambrano ] |
Arturo Zambrano
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Liana Munroe
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Arturo Zambrano
made changes -
Summary | Add "Reset" capability to ACE, MOBI components | Add "Clear" capability to ACE, MOBI components |
Arturo Zambrano
made changes -
Description |
A useful feature for an application is to provide a "Reset" button on a form to allow the use to reset all form fields to their original states, prior to any user modifications.
Historically, the HTML input type="reset" was used for this function (e.g. " <input type="reset" value="Reset!">"). However, with the more advanced and complex components provided by ACE and MOBI, the basic form-field reset capability provided by the HTML input technique is no longer sufficient to ensure proper value resetting. This JIRA is to investigate and ultimately provide an easy to use mechanism for resetting all components in a form reliably, whether they be ACE, MOBI, or "h:" / standard JSF components. Note that this JIRA would likely provide a JavaScript-based mechanism for resetting the components in a form, but ultimately this JS function would be integrated into a new "reset" type for the existing ace:pushButton component (under a separate JIRA - |
A useful feature for an application is to provide a "Reset" button on a form to allow the use to reset all form fields to their original states, prior to any user modifications.
Historically, the HTML input type="reset" was used for this function (e.g. " <input type="reset" value="Reset!">"). However, with the more advanced and complex components provided by ACE and MOBI, the basic form-field reset capability provided by the HTML input technique is no longer sufficient to ensure proper value resetting. While, the native reset button not only clears input elements but also resets those elements to the values with which they were loaded initially, in the case of our components the notion of an original value is not straight-forward, since our components' values can be programmatically updated, and also ajax requests can save components' values multiple times in a user session. This makes it unclear to determine what really are the original components' values. This JIRA is to investigate and ultimately provide an easy to use mechanism for clearing all components in a form reliably, whether they be ACE, MOBI, or "h:" / standard JSF components. Note that this JIRA would likely provide a JavaScript-based mechanism for clearing the components in a form, but ultimately this JS function would be integrated into a new "clear" mode for the existing ace:pushButton component (under a separate JIRA - |
Arturo Zambrano
made changes -
Ken Fyten
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Affects | Documentation (User Guide, Ref. Guide, etc.) [ 10003 ] | |
Resolution | Fixed [ 1 ] |
Liana Munroe
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Ken Fyten
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Arturo Zambrano
made changes -
Liana Munroe
made changes -
Comment |
[ Tested with ICEfaces 4 trunk r 47630.
Issue found when using the Clear button in a form that has an ace:textEntry with a preloaded value and an inField label. If the Clear button is pressed before entering input into the ace:textEntry, newly entered input becomes part of the inField label. This issue seems to be exclusive to ace:textEntry. It is not an issue with ace:textAreaEntry, ace:maskedEntry, ace:dateTimeEntry etc. To reproduce: 1.) Use the QA test application /ClearResetSubmit.jsf found at: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Nightly/pushButton. 2.) Scroll down to Form 2. Notice the preloaded values in each input. 3.) Press the Clear button at the bottom of the form. Notice all inputs display the inField label. 4.) Insert the cursor into the ace:textEntry. The inField label is not removed as it should be. 5.) Type into the ace:textEntry. The new input becomes part of the inField label. 6.) Press the submit button. The newly typed input is removed and the inField label is redisplayed. ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |