You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Craig McClanahan (JIRA)" <de...@myfaces.apache.org> on 2007/02/11 08:05:05 UTC

[jira] Commented: (TOMAHAWK-894) User specified style classes do not behave as expected

    [ https://issues.apache.org/jira/browse/TOMAHAWK-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472070 ] 

Craig McClanahan commented on TOMAHAWK-894:
-------------------------------------------

It should go without saying that, if this kind of change is made to Tabbed Pane, the same philosophy would be consistently applied across the entire component library.



> User specified style classes do not behave as expected
> ------------------------------------------------------
>
>                 Key: TOMAHAWK-894
>                 URL: https://issues.apache.org/jira/browse/TOMAHAWK-894
>             Project: MyFaces Tomahawk
>          Issue Type: Bug
>          Components: Tabbed Pane
>    Affects Versions: 1.1.5-SNAPSHOT
>            Reporter: Craig McClanahan
>
> The TLD docs for the "t:panelTabbedPane" have these definitions for two of the style class overrides:
> activeTabStyleClass        Style class of the active tab cell
> inactiveTabStyleClass     Style class of the inactive tab cells
> This implies to the reader that I can say something like:
>     <t:panelTabbedPane ... activeTabStyleClass="menu-sel" inactiveTabStyleClass="menu" .../>
> and expect my custom style classes to take effect.  However, that is not what actually happens, because the component still emits the default Tomahawk style class first (myFaces_panelTabbedPane_activeHeaderCell or myFaces_panelTabbedPane_inactiveHeaderCell).  That means my styles get ignored *unless* I create a cascade in my stylesheet definitions, or I use the "!important" modifier on EVERY SINGLE ENTRY.  That is very poor usability -- it would be much better to *replace* the default style class when the user specifies one, so they don't have to go through all the pain of figuring out why their styles seem to be ignored.

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