Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-Beta2
-
Fix Version/s: 2.0.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:jsf2.0, ICEfaces2.0, ACE
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration
Description
Currently, the sliderEntry requires that the user specify a thumb image using the component's "thumbUrl" attribute.
Since this property is not likely to change unless the skin or image has changed, we should modify the component to use a thumb image specified in the skin CSS instead of the component attribute (remove comp. attribute).
link to show an example of the css classes to use is:-
http://developer.yahoo.com/yui/3/examples/slider/slider_from_markup.html
NOTE: The key requirement here is that we do not want to force the user to have to specify a thumb image as an attribute of the component. Instead, the skin CSS should specify the thumb image to use.
Is there a technical reason why this cannot be supported?
Since this property is not likely to change unless the skin or image has changed, we should modify the component to use a thumb image specified in the skin CSS instead of the component attribute (remove comp. attribute).
link to show an example of the css classes to use is:-
http://developer.yahoo.com/yui/3/examples/slider/slider_from_markup.html
NOTE: The key requirement here is that we do not want to force the user to have to specify a thumb image as an attribute of the component. Instead, the skin CSS should specify the thumb image to use.
Is there a technical reason why this cannot be supported?
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| Summary | sliderEntry not loading images / working since YUI 3.2.0 upgrade was completed | ACE: Modify sliderEntry so that images are loaded using css/skinning, and not via thumbImg attribute |
| Issue Type | Bug [ 1 ] | Improvement [ 4 ] |
| Salesforce Case | [] | |
| Affects | [Compatibility/Configuration] | [Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration] |
| Assignee Priority | P1 | P2 |
| Affects Version/s | 2.0-Beta2 [ 10242 ] | |
| Affects Version/s | 2.0.0 [ 10230 ] | |
| Description |
upon updating to yui3.20, it was noticed that the markup for sliderEntry shows the paths to images with escaping backslashes... for example:- "thumbUrl":"javax.faces.resource\/assets\/skins\/sam\/thumb-x.png.jsf?ln=yui\/3_2_0" Problem is in JSONBUilder placing in the escaping and the images won't load now (with 3.2.0). Since this property is not likely to change unless the skin or image has changed, then change to use the skinning/css to load the images. rather than using a param within the script to pass the image. link to show an example of the css classes to use is:- http://developer.yahoo.com/yui/3/examples/slider/slider_from_markup.html NOTE: The key requirement here is that we do not want to force the user to have to specify a thumb image as an attribute of the component. Instead, the skin CSS should specify the thumb image to use. |
Currently, the sliderEntry requires that the user specify a thumb image using the component's "thumbUrl" attribute. Since this property is not likely to change unless the skin or image has changed, we should modify the component to use a thumb image specified in the skin CSS instead of the component attribute (remove comp. attribute). link to show an example of the css classes to use is:- http://developer.yahoo.com/yui/3/examples/slider/slider_from_markup.html NOTE: The key requirement here is that we do not want to force the user to have to specify a thumb image as an attribute of the component. Instead, the skin CSS should specify the thumb image to use. Is there a technical reason why this cannot be supported? |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Assignee Priority | P2 | P1 |
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Assignee Priority | P1 |