search

jmpressjs / jmpress.js

A jQuery plugin to build a website on the infinite canvas
http://jmpressjs.github.com/jmpress.js
1.5k stars 237 forks source link

jmpress skipping transitions in all presentations on Firefox 31.0 #157

Closed dc-devs closed 9 years ago

dc-devs commented 9 years ago

I just downloaded Firefox 31.0 and noticed that ALL jmpress presentations are skipping from slide to slide with no animation.

Please see my site as well as jmpress's presentations below. http://www.displayadtech.com/the_display_advertising_technology_landscape http://jmpressjs.github.io/jmpress.js/

Am I the only one currently seeing this, could this be a simple configuration setting on my end? jimpress presentations still working as expected in Safari and Chrome.

Any help pointing in the right direct would be a great help.

Thanks!

TheDoctor05 commented 9 years ago

Try this: https://github.com/jmpressjs/jmpress.js/issues/154

dc-devs commented 9 years ago

Thank you! I deleted line 92 which was:

,transitionProperty: addComma(mapProperty(pfx('transform'))) + addComma(mapProperty(pfx('perspective'))) + 'opacity'

I can confirm my presentation does now work in FF31. I can also confirm that this presentation is still working as expected in Chrome 36.0.1985.125 and Safari 7.0.5 (9537.77.4).

freme commented 8 years ago

Thanks, now the animations do work in Chrome and FF

matatk commented 8 years ago

I am still experiencing this bug with what I believe is the latest version from npm - 0.4.5. It seems a PR was accepted to fix this, but it is occurring for me.

I found that the line of code that @DWC01 mentioned above is now line 91 in jmpress.js and removing it fixed the problem -- now slide transitions now work in Chrome (49) -- Firefox actually crashes for some reason when I run my presentation, but that was both before and after this edit to the codes I'm not sure that's your problem :-).

Are others seeing the reoccurrence of this bug too?

dc-devs commented 8 years ago

Hey @matatk,

I recently had success using the fix mentioned in https://github.com/jmpressjs/jmpress.js/issues/179 when pulling the latest jmpress version from npm...