I initially felt that animation should belong in the behaviour layer rather than presentation layer.
Then, after reading Tim’s article I pulled my stick out of the mud and thought fuck it. Why not?
When was the last time you styled a hover state with javascript?
Separating these two out is an artefact of the technologies we have had available for the past decade. We’ve not included animation and transition effects in our CSS because these have not previously been possible.
The web is now a fluid medium that moves in more than 2 dimensions. Design is a key part of this fluidity and by restricting our CSS to static compositions we are – as Tim has so adeptly demonstrated – severely limiting ourselves and the rich, engaging designs we can create in this medium.
I initially felt that animation should belong in the behaviour layer rather than presentation layer.
Then, after reading Tim’s article I pulled my stick out of the mud and thought fuck it. Why not?
When was the last time you styled a hover state with javascript?
Separating these two out is an artefact of the technologies we have had available for the past decade. We’ve not included animation and transition effects in our CSS because these have not previously been possible.
The web is now a fluid medium that moves in more than 2 dimensions. Design is a key part of this fluidity and by restricting our CSS to static compositions we are – as Tim has so adeptly demonstrated – severely limiting ourselves and the rich, engaging designs we can create in this medium.