struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WW-4166) Allow "class" attribute on Struts tags
Date Wed, 06 Aug 2014 12:03:12 GMT

    [ https://issues.apache.org/jira/browse/WW-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087587#comment-14087587
] 

Hudson commented on WW-4166:
----------------------------

SUCCESS: Integrated in Struts-JDK6-develop #72 (See [https://builds.apache.org/job/Struts-JDK6-develop/72/])
WW-4166 Uses .get instead [] to avoid potential security issues (lukaszlenart: rev 52481bd56dd70ddcb68a737c5724037ed9adbc83)
* core/src/main/resources/template/simple/dynamic-attributes.ftl


> 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)

Mime
View raw message