Re: supported browsers

Thanks for all the good feedback, everyone.

I would agree with Michael that we should be careful with using 
javascript to enable/disable features. I think our policy there should 
be something like: We only *enable* features using javascript, so w/o 
javascript == default, degraded state.

Jan, thanks for the links to bugs.kde.org. I've voted and added a 
comment re: Plone to the XMLHttpRequest bug (you already covered the 
other one, I noticed). :)

So we are looking at a four-level browser support policy. I think we 
should be specific about which UI features we are supporting at which 
level (and Tonico, I think this may help answer your concerns re: 
usability/UI standards):



1) Full DHTML Support (IE, Moz/FF, Nav)
-------------------------------------------------------
Includes: Epoz (but technically this isn't part of Plone, eh?)
           XMLHttpRequest (where is/will this be used?)
           everything supported at Level 2


2) Partial DHTML Support (Opera, Safari, Konqueror)
-------------------------------------------------------
Includes: action menus
           date widget
           "Navigational Plone Tabs(tm)" :p
           anything else here?
           everything supported at Level 3


3) CSS Support
-------------------------------------------------------
All *style* for anonymous Plone will be consistently displayed across 
all CSS2-supporting browsers.


4) Universal Info Access
-------------------------------------------------------
All *information* will be accessible by any user agent.




I feel like we're getting somewhere. :)




chad




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click