Is it? I think all that means is: "Your browser should support hardware accelerated CSS3 and have a fast Javascript VM". Isn't the standards-centric view pretty much the opposite of the browser-centric one?
The project already said what you suggest, in fact several times.
Roughly:
"It's a presentation framework based on the power of CSS3 transforms and transitions in modern browsers and inspired by the idea behind prezi.com."
More or less exactly what you said:
"Impress.js is developed with current webkit-based browsers in mind (Chrome, Safari), but should work also in other browsers supporting CSS3 3D transforms and transitions (Firefox, IE10)."
It even says it is tested with nightly builds of Firefox and _then_ came up with the previously quoted:
"I don't really expect it to run smoothly in non-webkit-based browser."
At this point the requirements are already defined, the tested browser setups are listed. This is just surprising insofar as that
- the text before says that Firefox Aurora is tested as well (I've to admit I missed that reading the explanation the first time)
- this (and that was my real point) becomes a ~standard~ disclaimer by now. Chrome it is, the rest be damned. I think that's sad and still stand by my comparison to 'IE optimization' for things like this.
Comments
Is it? I think all that means is: "Your browser should support hardware accelerated CSS3 and have a fast Javascript VM". Isn't the standards-centric view pretty much the opposite of the browser-centric one?
Well, no.
The project already said what you suggest, in fact several times.
Roughly: "It's a presentation framework based on the power of CSS3 transforms and transitions in modern browsers and inspired by the idea behind prezi.com."
More or less exactly what you said: "Impress.js is developed with current webkit-based browsers in mind (Chrome, Safari), but should work also in other browsers supporting CSS3 3D transforms and transitions (Firefox, IE10)."
It even says it is tested with nightly builds of Firefox and _then_ came up with the previously quoted:
"I don't really expect it to run smoothly in non-webkit-based browser."
At this point the requirements are already defined, the tested browser setups are listed. This is just surprising insofar as that
- the text before says that Firefox Aurora is tested as well (I've to admit I missed that reading the explanation the first time)
- this (and that was my real point) becomes a ~standard~ disclaimer by now. Chrome it is, the rest be damned. I think that's sad and still stand by my comparison to 'IE optimization' for things like this.
True, but majority of the users doesn't know if their browser supports hardware accelerated CSS3 and has fast JS VM. And they probably don't care.
Listing browsers (or with hardware acceleration browsers+systems) helps to know what configuration can be used to make it work.
In that case "webkit-based" won't help non-technical users either :)