struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WW-4166) Allow "class" attribute on Struts tags
Date Mon, 28 Jul 2014 18:56:40 GMT

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

ASF subversion and git services commented on WW-4166:
-----------------------------------------------------

Commit 6fbd1bef3a91eb6992507086b75f6d22bcb95fb2 in struts's branch refs/heads/develop from
[~lukaszlenart]
[ https://git-wip-us.apache.org/repos/asf?p=struts.git;h=6fbd1be ]

WW-4166 Adds class and style aliases


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