Details
-
Type: Task
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: EE-2.0.0.Alpha1
-
Fix Version/s: EE-2.0.0.Beta1
-
Component/s: Facelet Components
-
Labels:None
-
Environment:ICEfaces EE 2.0
Description
The slider component was removed from EE 2.0 alpha because a similar component was no part of ACE components and there was JavaScript compatibility issues with YUI that is in the ICEfaces bridge.
The idea here is to add the slider component back but have it wrap the new ace slider component.
The idea here is to add the slider component back but have it wrap the new ace slider component.
Activity
Patrick Corless
created issue -
Patrick Corless
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Brad Kroeger [ brad.kroeger ] | Patrick Corless [ patrick.corless ] |
Patrick Corless
made changes -
Salesforce Case | [] | |
Fix Version/s | EE-2.0.0.Beta1 [ 10254 ] |
Patrick Corless
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
For compatibility reasons the old slider is being added back to the EE components. Instead of a separate implementation the ice-cc:slider now simply wraps the ace slideEntry component. In doing so there are few functional changes that need to be considered mainly around attributes of the ice-cc:slider.
updateOnEvent - attribute is no deprecated and no lunger has any functional meaning.
singleSubmit - new attribute that is similar to updateOnEvent that when singleSubmit=false the compoennt will no longer submit its value on focus lost instead waiting until the entire form has been submitted.
Another big side effect of the ace comonent is that we can no longer use the YUI libraries included with the CC components as they collide with the icefaces ace libraries. It is my understanding that because we use the ace component in the ee component there is no need to bother with loading yui.