[
https://issues.apache.org/jira/browse/WW-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087344#comment-14087344
]
Lukasz Lenart edited comment on WW-4166 at 8/6/14 6:57 AM:
-----------------------------------------------------------
Not sure what you mean by ??apply this patch to all version especially version
before 2.3.18.?? - we don't do that, if so we can prepare another fast-track
release if this is a security issue.
was (Author: lukaszlenart):
Not sure what you mean by ??apply this patch to all version especially version
before 2.3.18.?? - we won't do that, if so we can prepare another fast-track
release if this is a security issue.
> Allow "class" attribute on Struts tags
> --------------------------------------
>
> Key: WW-4166
> URL: https://issues.apache.org/jira/browse/WW-4166
> Project: Struts 2
> Issue Type: Improvement
> Components: Other
> Reporter: Eric Lentz
> Assignee: Lukasz Lenart
> Priority: Trivial
> Fix For: 2.3.18
>
>
> In building a JSP, and working on web related things outside of the Java
> environment, there are lots of tags which all receive the "class" attribute.
> The Struts developer must _remember_ to call the attribute cssClass instead.
> Typing muscle memory drives me to half of the time typing "class" instead,
> which leads to HTML which reads, 'class="class java.util.HashMap"'
> Why not just allow "class" like the rest of the HTML world? Why do we need to
> be different? I have a billion things to remember when web developing, this
> shouldn't be one of them.
> We don't even have to to deprecate or obsolete cssClass, just also allow
> "class"... please!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
