You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Brian Ploetz (JIRA)" <ji...@apache.org> on 2007/08/01 16:56:05 UTC
[jira] Created: (WW-2080) fielderror.ftl in the simple theme does
not honor the cssClass or cssStyle attributes
fielderror.ftl in the simple theme does not honor the cssClass or cssStyle attributes
-------------------------------------------------------------------------------------
Key: WW-2080
URL: https://issues.apache.org/struts/browse/WW-2080
Project: Struts 2
Issue Type: Bug
Components: Views
Affects Versions: 2.0.9
Reporter: Brian Ploetz
Setting the "cssClass" or "cssStyle" attributes on a <s:fielderror> tag has no impact. The fielderror.ftl file uses a hard coded css class "errorMessage":
<ul>
<#list eKeys as eKey><#t/>
<#assign eValue = fieldErrors[eKey]><#t/>
<#list eValue as eEachValue><#t/>
<li><span class="errorMessage">${eEachValue}</span></li>
</#list><#t/>
</#list><#t/>
</ul>
If you take a look at another tag which does honor the cssClass and cssStyle attributes, they look for the existence of these attributes and swap them in if they're specified. For example, select.ftl:
<#if parameters.cssClass?exists>
class="${parameters.cssClass?html}"<#rt/>
</#if>
<#if parameters.cssStyle?exists>
style="${parameters.cssStyle?html}"<#rt/>
</#if>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WW-2080) actionError, actionMessage and fieldError
Freemarker templates do not honor the cssClass and cssStyle attributes
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Holmes updated WW-2080:
-----------------------------
Summary: actionError, actionMessage and fieldError Freemarker templates do not honor the cssClass and cssStyle attributes (was: fielderror.ftl in the simple theme does not honor the cssClass or cssStyle attributes)
> actionError, actionMessage and fieldError Freemarker templates do not honor the cssClass and cssStyle attributes
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WW-2080
> URL: https://issues.apache.org/struts/browse/WW-2080
> Project: Struts 2
> Issue Type: Bug
> Components: Views
> Affects Versions: 2.0.9
> Reporter: Brian Ploetz
> Assignee: James Holmes
>
> Setting the "cssClass" or "cssStyle" attributes on a <s:fielderror> tag has no impact. The fielderror.ftl file uses a hard coded css class "errorMessage":
> <ul>
> <#list eKeys as eKey><#t/>
> <#assign eValue = fieldErrors[eKey]><#t/>
> <#list eValue as eEachValue><#t/>
> <li><span class="errorMessage">${eEachValue}</span></li>
> </#list><#t/>
> </#list><#t/>
> </ul>
> If you take a look at another tag which does honor the cssClass and cssStyle attributes, they look for the existence of these attributes and swap them in if they're specified. For example, select.ftl:
> <#if parameters.cssClass?exists>
> class="${parameters.cssClass?html}"<#rt/>
> </#if>
> <#if parameters.cssStyle?exists>
> style="${parameters.cssStyle?html}"<#rt/>
> </#if>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (WW-2080) fielderror.ftl in the simple theme does
not honor the cssClass or cssStyle attributes
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Holmes reassigned WW-2080:
--------------------------------
Assignee: James Holmes
> fielderror.ftl in the simple theme does not honor the cssClass or cssStyle attributes
> -------------------------------------------------------------------------------------
>
> Key: WW-2080
> URL: https://issues.apache.org/struts/browse/WW-2080
> Project: Struts 2
> Issue Type: Bug
> Components: Views
> Affects Versions: 2.0.9
> Reporter: Brian Ploetz
> Assignee: James Holmes
>
> Setting the "cssClass" or "cssStyle" attributes on a <s:fielderror> tag has no impact. The fielderror.ftl file uses a hard coded css class "errorMessage":
> <ul>
> <#list eKeys as eKey><#t/>
> <#assign eValue = fieldErrors[eKey]><#t/>
> <#list eValue as eEachValue><#t/>
> <li><span class="errorMessage">${eEachValue}</span></li>
> </#list><#t/>
> </#list><#t/>
> </ul>
> If you take a look at another tag which does honor the cssClass and cssStyle attributes, they look for the existence of these attributes and swap them in if they're specified. For example, select.ftl:
> <#if parameters.cssClass?exists>
> class="${parameters.cssClass?html}"<#rt/>
> </#if>
> <#if parameters.cssStyle?exists>
> style="${parameters.cssStyle?html}"<#rt/>
> </#if>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2080) actionError, actionMessage and
fieldError Freemarker templates do not honor the cssClass and cssStyle
attributes
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41708 ]
James Holmes commented on WW-2080:
----------------------------------
Thanks for the heads up!
This was fixed on the Struts 2_0_X branch in SVN revision 561850.
> actionError, actionMessage and fieldError Freemarker templates do not honor the cssClass and cssStyle attributes
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WW-2080
> URL: https://issues.apache.org/struts/browse/WW-2080
> Project: Struts 2
> Issue Type: Bug
> Components: Views
> Affects Versions: 2.0.9
> Reporter: Brian Ploetz
> Assignee: James Holmes
>
> Setting the "cssClass" or "cssStyle" attributes on a <s:fielderror> tag has no impact. The fielderror.ftl file uses a hard coded css class "errorMessage":
> <ul>
> <#list eKeys as eKey><#t/>
> <#assign eValue = fieldErrors[eKey]><#t/>
> <#list eValue as eEachValue><#t/>
> <li><span class="errorMessage">${eEachValue}</span></li>
> </#list><#t/>
> </#list><#t/>
> </ul>
> If you take a look at another tag which does honor the cssClass and cssStyle attributes, they look for the existence of these attributes and swap them in if they're specified. For example, select.ftl:
> <#if parameters.cssClass?exists>
> class="${parameters.cssClass?html}"<#rt/>
> </#if>
> <#if parameters.cssStyle?exists>
> style="${parameters.cssStyle?html}"<#rt/>
> </#if>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (WW-2080) actionError, actionMessage and
fieldError Freemarker templates do not honor the cssClass and cssStyle
attributes
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on WW-2080 started by James Holmes.
> actionError, actionMessage and fieldError Freemarker templates do not honor the cssClass and cssStyle attributes
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WW-2080
> URL: https://issues.apache.org/struts/browse/WW-2080
> Project: Struts 2
> Issue Type: Bug
> Components: Views
> Affects Versions: 2.0.9
> Reporter: Brian Ploetz
> Assignee: James Holmes
>
> Setting the "cssClass" or "cssStyle" attributes on a <s:fielderror> tag has no impact. The fielderror.ftl file uses a hard coded css class "errorMessage":
> <ul>
> <#list eKeys as eKey><#t/>
> <#assign eValue = fieldErrors[eKey]><#t/>
> <#list eValue as eEachValue><#t/>
> <li><span class="errorMessage">${eEachValue}</span></li>
> </#list><#t/>
> </#list><#t/>
> </ul>
> If you take a look at another tag which does honor the cssClass and cssStyle attributes, they look for the existence of these attributes and swap them in if they're specified. For example, select.ftl:
> <#if parameters.cssClass?exists>
> class="${parameters.cssClass?html}"<#rt/>
> </#if>
> <#if parameters.cssStyle?exists>
> style="${parameters.cssStyle?html}"<#rt/>
> </#if>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WW-2080) actionError, actionMessage and
fieldError Freemarker templates do not honor the cssClass and cssStyle
attributes
Posted by "James Holmes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Holmes resolved WW-2080.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0.10
Fixed on the trunk (Struts 2.1) in SVN revision 561856.
> actionError, actionMessage and fieldError Freemarker templates do not honor the cssClass and cssStyle attributes
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WW-2080
> URL: https://issues.apache.org/struts/browse/WW-2080
> Project: Struts 2
> Issue Type: Bug
> Components: Views
> Affects Versions: 2.0.9
> Reporter: Brian Ploetz
> Assignee: James Holmes
> Fix For: 2.0.10
>
>
> Setting the "cssClass" or "cssStyle" attributes on a <s:fielderror> tag has no impact. The fielderror.ftl file uses a hard coded css class "errorMessage":
> <ul>
> <#list eKeys as eKey><#t/>
> <#assign eValue = fieldErrors[eKey]><#t/>
> <#list eValue as eEachValue><#t/>
> <li><span class="errorMessage">${eEachValue}</span></li>
> </#list><#t/>
> </#list><#t/>
> </ul>
> If you take a look at another tag which does honor the cssClass and cssStyle attributes, they look for the existence of these attributes and swap them in if they're specified. For example, select.ftl:
> <#if parameters.cssClass?exists>
> class="${parameters.cssClass?html}"<#rt/>
> </#if>
> <#if parameters.cssStyle?exists>
> style="${parameters.cssStyle?html}"<#rt/>
> </#if>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.