Wed, 2011-12-14 15:28
Hi,
I am wondering what the forum's thoughts are on CSS3 and it's inclusion of features such as animation. Surely animation is _not_ part of a site's layout. Style sheets are used to format the layout of Web pages, not create animation.
Correct me if I'm wrong.
Wed, 2011-12-14 16:31
#1
I wouldn't worry too much, in
I wouldn't worry too much, in a sense all is going to pot they will try and add more and more behaviour into CSS probably. We are entering a dev world where people want bells and whistles - and why not? - over good firm standards and best coding practises. CSS3, HTML5 both address things we have moaned about for an age but also have that slight feeling of pandering to the crowd that just want an easy in to frontend coding?.
By and large CSS3 is a good thing or rather that browsers have finally caught up and we are able to use more of the properties is a blessing, so I for one will overlook 'animation'.
Wed, 2011-12-14 19:07
#2
Personally, I think that
Personally, I think that "layout" refers to anything and everything that deals with how data is displayed. That includes, size, position, color, font, but indeed also movement/animation.
Back end is responsible for making sure the correct data is being fed to the browser.
Front end is responsible for making sure this data is presented properly.
Just my personal opinion.
Wed, 2011-12-14 21:28
#3
Yeah but historically and
Yeah but historically and otherwise frontend is split into presentational layer and behaviour layer, behaviours were always thought of as not belonging to the presentation layer.
Wed, 2011-12-14 22:10
#4
There is definitely a blur
There is definitely a blur between the presentation and behaviour layers now. Looks like they are trying to get rid of JavaScript or just keep it around for AJAX type functionality.
Wed, 2011-12-14 22:18
#5
It feels like an upgrading
It feels like an upgrading of the status of javascript in a sense; some of the simpler things one might have done and required using a client side scripting language are simply available via an undetermined browser action , thinking of things like HTML5 form attrs 'required', 'placeholder', 'pattern matching' although this strays from the CSS3 start of this thread.