Firefox 14 breaking Edge animations, why?
Can anyone from Mozilla or just general developers explain why FF has decided to change the handling of CSS3 animations? This primarily breaks most of the functionality of the Adobe Edge software. Any info would be great!
The main issues are items not locating correctly on the screen, and some transitions not occurring as they should.
Eminye Imininingwane Yohlelo
- Shockwave Flash 11.3 r300
- Office Live Update v1.0
- Java Plug-In 2 for NPAPI Browsers
- The QuickTime Plugin allows you to view a wide variety of multimedia content in web pages. For more information, visit the QuickTime Web site.
- The Flip4Mac WMV Plugin allows you to view Windows Media content using QuickTime.
- I-ejenti Engumsebenzisi: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20100101 Firefox/14.0.1
Could you provide a link to an animation that worked in Firefox 13 and is broken in Firefox 14? Then we could look at the CSS and see if we can spot the problem.
Meanwhile, you might also check Adobe's forums and see whether they have any recent threads or updates in anticipate of Firefox 14's release.
There is a statement on the Adobe website that they are working on a fix
"Firefox 14 was released today and they've made some tweaks to their animation spec. Due to these tweaks CSS animations across the web will be affected (these issues aren't necessarily specific to Edge). There isn't a workaround you can use with Preview 6, however we ask that you sit tight while we explore options for a fix. We understand this is a high priority problematic issue and apologize for the inconvenience its causing."
Please note that CSS properties that have a vendor prefix are experimental and not stable, which means that they can be modified at any time. Therefore they should not be used on production websites.
Okulungisiwe ngu knorretje
I also have the same problem with http://mercuriopublicidad.com
The main change to transforms in Firefox 14 is that the nonstandard skew() method was removed. When I look at the edge.0.1.6.min.js library, I can't figure out how to edit the code to address that change. Perhaps there is a better documented (non-minified) copy of the file that could be used for experiments. Or, it wouldn't surprise me if we start seeing articles and blog posts with solutions in the next few days.
Okulungisiwe ngu jscher2000
It seems to be much more than the skew() method, unless Edge based all of their transformations off that. Scaling of images, location on screen, and movement have all been broken by FF14. More of this might be on Adobe's shoulders for developing software that used parameters that are not set. I also wonder if this is just a bug in FF?
That's great Mozilla, you add a method into your browser, instruct users on how to work with it, then remove it, yet still leave the instructions up?
It seems like a big step back for CSS3 if they are removing this. Does anyone know why they are removing this, functionality was great, even on iOS.
Hi lswing, the two methods in the (draft?) standard are skewX(angle) and skewY(angle). In other words, the two parameters need to be specified separately rather than in one skew(angleX, angleY). I don't know who is deciding the timing of removing nonstandard methods. I'm not convinced these changes are really necessary; there probably is a less painful way to encourage standards conformance than removing nonstandard properties and methods.
Same problem here. http://www.portoffolio.com/port-of-folio---assorted-illustration.html
Seems odd that the change would need to be made on Adobe's side, in that, (according to Adobe) css animations created outside of Adobe Edge are experiencing problems as well. This will be asking a lot of developers to go back in and tweak their code after the fact that it used to work and works on all other relevant browsers.
I've seen some posts between Mozilla and Edge regarding svg canvas-based animation... http://forums.adobe.com/thread/884525
Is there some connection with this latest problem... weeding out the unwanted??
Edge has released a fix, 6.1. Should do it. Resolves and recodes old files with the updated Transition language. Thanks for the input all!
From Adobe's website: Our team has devised a remedy for the problem, and it is available today as Adobe Edge preview 6.1. You can download it from Adobe Labs or via the Creative Cloud. After you install it, all you’ll have to do is resave your project(s) and it will work in Firefox. Alternatively, you can simply swap out the runtime files without having to reload the composition in the app.
I'm not a developer, just owner of a website that is now broken. What is meant by "swap out the runtime files"? I installed Edge 6.1 locally, so I assume I need to copy some files to my web server, but which ones?
Is the person/company who developed your animation not offering support?
Not sure about the swap out runtime files statement.
It's a matter of installing 6.1, opening the edge file, then saving (so they say, I have yet had the chance). Now....there is a chance that could cause some major issues if the person who programmed you edge file made changes after edge, as I do.
I would suggest getting in touch with whomever made the animation, or another developer that understands the code. Good luck!
So, I put the new run-time files in place, but still no joy. Anyone have any ideas? I'll buy you a beer...
I just opened the stuff in Edge pressed save and reupped. Works like a charm again for me.