📜 ⬆️ ⬇️

Adobe Edge Animation, Chrome 23 and Brain Promotions Post

The following story - we are doing a web project. The customer wants it to be beautiful as on a flash, but not on a flash, because it is necessary on the iPad. OK. We take some Adobe Edge (then another 0.6) as a tool for creating complex animation on js \ CSS3 \ HTML5. Everything turns out. Wow. While we are going to the production - Edge goes to the release, class!

Some time passed and now Edge was released. 1.0.0.0, however !!!
We supplement, put for the release preview to the customer, and in response: “what is this for ...?”


')
Khm Further complete sur - because we are fine, but he has some obscene expressions.

And this is what happened: Chrome 23 is out! But not at all, but rather not immediately. In the end, I have Chrome 22 and everything is fine, and the customer has Chrome 23 and is antonymous. And what is the problem, what has changed there? requestAnimationFrame fell off? gpuAcceleration in the browser disconnected? Did SSSS3 have time to peer-standardize?

But they did not guess. The whole secret in brain protuberances:

--- edge.1.0.0.min.js ----
j = navigator.userAgent;
if (/Chrome\/21/.test(j) || /Chrome\/22/.test(j) )
this.gpuAccelerate = !0;

so here. And nothing else. Those. The browser quietly, at midnight, has been updated - and your precious saEt turns into a pumpkin, oops. Buy our elephants, or rather - use Adobe Edge, more often.

Source: https://habr.com/ru/post/157791/


All Articles