There is no reason why you can't use CSS directly, without using a label, a label just makes it easy to format your text cross browser.
NS4 support does  not suffer from using CSS directly, it just doesn't look as good, but simply ignores what it can't render.
You can do something like this:
 
    myLayer.css.filter = 'alpha(opacity=40)';
 
This would make a layer nicely transparent in IE5, NS4 would ignore it. But if you want NS6 to do the same, you have to do this:
 
    myLayer.css.MozOpacity = '40%'
 
So there go your standards!
You can't only support NS6 and Mozilla.
On the other hand you are right that DynAPI should follow the w3c standards as close as possible, but it should offer degrading for older browsers. A work in progress I guess.
(These examples are taken from Ruairi's excellent transparency widget) 
 
Cheers,
Richard Bennett
 
[EMAIL PROTECTED]
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)
Find the DynAPI faq here:
http://sourceforge.net/docman/display_doc.php?docid=656&group_id=5757
Browse the mailinglist here:
http://www.mail-archive.com/index.php3?hunt=dynapi
 
----- Original Message -----
Sent: Tuesday, March 06, 2001 5:28 PM
Subject: [Dynapi-Dev] Suggestions for the DynAPI - Part 2

Why should I have to use a label in order to implement a style that is
defined in the CSS1 Specification?

Shouldn't the DynAPI attempt to follow W3C standards as much as possible?

Both CSS1 and CSS2 have been approved and if we are in fact seeking to build
a cross-browser system for using style sheets, layers, divs, or whatever you
want to call them, then shouldn't we be adhering to the standards that have
been approved and requested?

Just my thoughts on the whole thing and I really don't the ins and outs of
the DynAPI that well to understand why it is that some methods can or cannot
be implemented.   

As far as it goes for now, I guess that I will continue to use pure CSS and
Javascript without the DynAPI since being able to create sites that do what I
want when I want without limitations is a must.

I also believe that I should mention the fact that continuing to provide
support for browsers that do not properly support standards is a waste of not
only our time, but our site visitors time.  I wouldn't have even suggested to
any user that they update the browser they are using a year or two ago.  But
these days just about everyone has the ability to connect at 56K and most of
the people that I am marketing to on the sites that I build are most likely
going to have the ability to update and will probably have already done so.

Reply via email to