You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xap-dev@incubator.apache.org by "Turyn, Michael (JIRA)" <xa...@incubator.apache.org> on 2007/05/04 03:11:15 UTC

[jira] Resolved: (XAP-344) Should support a passthrough mechanism for setting up css classes on components

     [ https://issues.apache.org/jira/browse/XAP-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Turyn, Michael resolved XAP-344.
--------------------------------

    Resolution: Fixed

See comments.

> Should support a passthrough mechanism for setting up css classes on components
> -------------------------------------------------------------------------------
>
>                 Key: XAP-344
>                 URL: https://issues.apache.org/jira/browse/XAP-344
>             Project: XAP
>          Issue Type: New Feature
>          Components: Widgets: Other
>            Reporter: James Margaris
>         Assigned To: Turyn, Michael
>
> Right now there is no good way to assign custom classes to widgets. I propose:
> 1. All xal elements should support the class attribute which is a space-separated list of classes. 
> 2. For each entry in the attribute we should assign that entry to the base HTML container node/ root dom node. (Simply pass through to the underlying HTML tag)
> 3. In addition we want to support the various style states. So if they have a class called myClass we should automatically adjust that to myClassMouseOver the same way we do for built-in classes. Currently we have logic in AbstractWidgetBridge that will automatically change the class attribute to different permuations of the tag name, like "buttonMouseOver", "buttonMouseDown", etc. We should allow user-defined classes to use the same process and automatically add/remove state-specific permutations with mouse events.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.