W3C home > Mailing lists > Public > www-style@w3.org > May 2006

Re: [CSS3] transition effects -why not use proper scripting backed up by the correct DOM methods?

From: Jordan OSETE <jordan.osete@laposte.net>
Date: Wed, 10 May 2006 08:05:12 +0200
Message-ID: <44618298.7000007@laposte.net>
To: Andrew Fedoniouk <news@terrainformatica.com>
CC: www-style@w3.org

Andrew Fedoniouk a écrit :
> 
> 
> ----- Original Message ----- From: "Emrah BASKAYA" 
>> I do understand the problem of having to put style related information 
>> right in the javascript, but these things are too heavy for CSS, IMHO: 
>> just because we don't want to update two files (css+javascript) 
>> instead of one shouldn't mean CSS should hold the burden of these 
>> behaviours. However, I do understand the problem of having to declare 
>> style in Javascript.
> 
> 
> Main motivation:  I (as anyone else) would like to be able to 
> disable/enable transitions and similar effects in my UA.
> 
> Having animations defined in script does not allow me to implement this
> feature on UA's level.

That is exactly why events in CSS are here for. I am sorry i have not 
explained this well, but it's possible with that. If the script taking 
care of animations, transitions or whatever are with the main 
"behavioral" script (as it is the case right now, since there is no way 
to separate them), then there is no way for the UA to understand wich 
script does what. If you allow to put script in CSS, then the user agent 
can just have a "disable scripts defined in CSS" option, that will just 
do what you want.

Jordan Osete
Received on Wednesday, 10 May 2006 06:05:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:45 GMT