given they are doing it with -engine-rule their shouldn't be a problem (the
w3c recommends this method for non standard rules).
e.g you could have an opacity rule like :
.foo {
opacity : 50;
-moz-opacity : 50;
-khtml-opacity : 50;
/* whatever the MS filter one is */
}
and the browser engine should pick up the one it supports best. As the
engines work out any bugs with opacity (for example) they will hopefully end
up using opacity : 50; and you will end up with something like this,
assuming MS sits on their keyboards.
.foo {
opacity : 50;
/* whatever the MS filter one is */
}
On 2/10/07, Mordechai Peller <[EMAIL PROTECTED]> wrote:
Paul Bennett wrote:
> Isn't this the 2007 equivalent of the <blink> and <marquee> tags we all
know and hate?
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
