Mailing-List: contact issues-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@struts.apache.org
Date: Mon, 4 Aug 2014 19:16:13 +0000 (UTC)
From: "Lukasz Lenart (JIRA)" <jira@apache.org>
To: issues@struts.apache.org
Message-ID: <JIRA.12661383.1375443496931.9665.1407179773893@arcas>
In-Reply-To: <JIRA.12661383.1375443496931@arcas>
References: <JIRA.12661383.1375443496931@arcas>
Subject: [jira] [Commented] (WW-4166) Allow "class" attribute on Struts tags
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lukasz Lenart commented on WW-4166:
-----------------------------------

This looks good, with tiny change I'm going to push it, thanks!

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