- From: Matthew Raymond <mattraymond@earthlink.net>
- Date: Sat, 09 Dec 2006 10:26:06 -0500
- To: Andrew Fedoniouk <news@terrainformatica.com>
- CC: www-style@w3.org
Andrew Fedoniouk wrote: > From: "David Woolley" <david@djwhome.demon.co.uk> > | I agree with others that this is behaviour, and doesn't belong in > | CSS. > > behavior is a module of CSS3 as far as I can see: > http://www.w3.org/TR/css3-roadmap/#becss Considering XBL 2.0 is further along (Last Call) and is vastly superior, I'd suggest we use that for binding behavior instead of a spec that hasn't been updated in over seven year. > So it already belongs to CSS somehow. Sort of. You should be able to bind presentational behavior via CSS, but behaviors themselves should not be defined within CSS. > Speaking about animations as behaviors... > Let's assume we have some set of "standard" behaviors, then: > > Master style sheet of some UA will be able to use: > > img:animation { behaivor: animate-image; } > > And user will be able to define: > > img:animation { behaivor: none; } > > on his/her end. Other than the fact that these behaviors are built-in rather than created via a binding language, this isn't functionally different from XBL2. I would suggest, however, that canned behaviors are better suited as a follow-up spec to XBL 2.0 and thus out of the scope of www-style. > But behaviors define logic of actions. > Animation in its turn is presentation atribute rather than > logic. So it is under CSS umbrella I beleive. Personally, I don't see anything wrong with simple animation control for images, like "background-image-animation" or something. For instance, you may want an animated GIF to be limited to a specific frame range. Why is positioning and clipping of an image in space presentational and positioning and clipping in time behavioral? Seems a little arbitrary.
Received on Saturday, 9 December 2006 15:27:24 UTC