Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Alpha3
-
Component/s: ICE-Components
-
Labels:None
-
Environment:ICEfaces 2 sparkle
Description
The sparkle input components, like checkbox and slider, render their value into a javascript hashtable, and don't use input fields. Because of this, if the application changes the component's value, when it's submitted, back to the original value, or to some other value, then the standard DOMPartialViewContext.applyBrowserChanges(-) mechanism won't work with it. Slider has code in it, to work-around this issue. So, either we find a way to make the sparkle input components work with applyBrowserChanges(-), or we replicate the slider work-around in each sparkle input component.
One approach would be, as we change the input components to do the proper partialSubmit behaviour, to use hidden input fields, or regular input fields, which will then be handled by applyBrowserChanges(-).
One approach would be, as we change the input components to do the proper partialSubmit behaviour, to use hidden input fields, or regular input fields, which will then be handled by applyBrowserChanges(-).
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
checkbox component has been modified to use a hidden field (both directions from and to server to accommodate server-push). The yui-checked value updates the hidden field and the value from the server passes through from the renderer to the client-side and updates the yui checked value.
The checkbox component no longer uses the javascript hashtable at all, but makes use of the hidden field.