OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [wsrp] Container vs content in menu items



I touched base with the expert dealing with CSS styles for menus regarding his comments about needing both container and content level classes.

The basic reasons for this need relate to wanting to reuse classes across multiple menu layout styles. For some layout styles, style attributes, such as font-color, do not inherit to the container's children. His recommendation is to define a set of generic portlet-menu-content classes (i.e. independent of what elements might actually be used to render the menu content). This would result in adding:

portlet-menu-content
portlet-menu-content-selected
portlet-menu-content-hover
portlet-menu-content-hover-selected

Any objections to adding these?

Rich


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]