[jira] Resolved: (WW-2484) Styles from templateCssPath ignored

["Musachy Barroso (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/struts/browse/WW-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Musachy Barroso resolved WW-2484.
---------------------------------

    Resolution: Cannot Reproduce

This is what I did to replicate this problem:

1. Go to /struts2-showcase/src/main/webapp/tags/ui/datepicker/index.jsp and add this to the file:

<s:url var="css" value="/styles/test.css" includeContext="false"/>
<sx:datetimepicker label="toggleType='wipe'" value="%{'2006-10-31'}" name="test" templateCssPath="%{#css}"/>

2. create test.css under /struts2-showcase/src/main/webapp/styles/test.css with this content:

.calendarContainer {
	width: 500px;
}

open the page in show case, the dropdown was 500px wide, as expected. My guess is that either your css is not being found (bad url), or there some sort of css problem (conflict/selector precedence). Drop an email to the user list as several people have done this before, and talked about it on the list. 




> Styles from templateCssPath ignored
> -----------------------------------
>
>                 Key: WW-2484
>                 URL: https://issues.apache.org/struts/browse/WW-2484
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Plugin - Dojo Tags
>    Affects Versions: 2.0.11, 2.0.11.1, 2.0.12, 2.1.0, 2.1.1
>            Reporter: Mike Calmus
>             Fix For: 2.1.3
>
>
> I copied the normal DatePicker.css to a local directory and made some changes. When I use the following tag:
>   <s:datetimepicker name="startDate" id="startDate" templateCssPath="/stylesheets/customDatePicker.css" displayFormat="MM/dd/yyyy" />
> The styles specified in the modified file, though are not used. Running the popup through FireBug (https://addons.mozilla.org/en-US/firefox/addon/1843) shows that the modified styles are all overriden by the default styles. In effect, those specified by the templateCssPath are ignored.
> I assume this is some sort of Dojo issue. Perhaps upgrading to dojo 0.9+ would fix it?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.