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: Re: [wsrp] menu CSS class


I have a broader comment on spec-defined styles in general. There are a 
wide variety of things that can be accomplished by clever use of CSS and 
I doubt if we will be able to capture all possibilities. This problem 
would be simplified if the spec lets portlets specify CSS classes that 
the portlet markup depends on.

Something to work on for V3.

Subbu

Mike Caffyn wrote:
> Rich,
> 
>  
> 
> Looks good, I seem to remember in one of the interop sites there was 
> portlet with a cascade menu that didn’t look quite right at the top level.
> 
>  
> 
> Mike
> 
>  
> 
> ------------------------------------------------------------------------
> 
> *From:* Rich Thompson [mailto:richt2@us.ibm.com]
> *Sent:* Monday, January 23, 2006 8:36 AM
> *To:* wsrp@lists.oasis-open.org
> *Subject:* [wsrp] menu CSS class
> 
>  
> 
> 
> As part of updating the menu example in the spec, I created a small test 
> file that roughly reproduces what had previously been drawn in an editor 
> using html and CSS. The one class I found to be missing in doing this 
> was portlet-menu-cascade. This is an equivalent to portlet-menu at the 
> top level, but allows things like having the border around the submenu 
> match the text color in portlet-menu-item-hover. Any objections to 
> adding this class?
> 
> Rich
> 
> *Rich Thompson/Watson/IBM@IBMUS*
> 
> 01/20/06 07:23 AM
> 
> 	
> 
> To
> 
> 	
> 
> wsrp@lists.oasis-open.org
> 
> cc
> 
> 	
> 
>  
> 
> Subject
> 
> 	
> 
> [wsrp] portlet-menu-description CSS class
> 
>  
> 
>  
> 
> 	
> 
>  
> 
> 
> 
> 
> 
> I agreed yesterday to start this email thread.
> 
> We had feedback from CSS experts that the portlet-menu-description class 
> appears inappropriate. In particular, it violates a number of UI 
> guidelines used on various platforms and would be problematic for screen 
> readers. The equivalent functionality is normally provided using 
> tooltips, but these are handled via the underlying windowing system 
> rather than being styled through CSS.
> 
> The questions we were all asked to investigate:
> 
> 1. Do other CSS experts agree with this evaluation of the 
> portlet-menu-description?
> 2. Is the portlet-menu-description class in use (i.e. would it be 
> disruptive to remove it)?
> 
> As we are trying to move rapidly toward a "Committee Draft" level of the 
> spec, early feedback on these questions would be great!
> 
> Rich 
> --------------------------------------------------------------------- To 
> unsubscribe from this mail list, you must leave the OASIS TC that 
> generates this mail. You may a link to this group and all your TCs in 
> OASIS at: 
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> --------------------------------------------------------------------- To 
> unsubscribe from this mail list, you must leave the OASIS TC that 
> generates this mail. You may a link to this group and all your TCs in 
> OASIS at: 
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 



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