Hi Tj.

getting this error in Firefox 4.0.1 (pc) when I try the demos on the docs page when I Press play on the first demo works fine in chrome

http://visionmedia.github.com/move.js/

uncaught exception: [Exception... "Not enough arguments" nsresult: "0x80570001 (NS_ERROR_XPC_NOT_ENOUGH_ARGS)" location: "JS frame :: http://visionmedia.github.com/move.js/move.min.js :: <TOP_LEVEL> :: line 5" data: no]

This pull request solves issue/41, issue/42 and issue/71, the first two relating to missing package.json, missing npm entry and therefore missing browserify support. The issue/41 has many details about the issue and its solution. After the merge, move.js can be downloaded via npm and used with browserify but still continued to be used with component(1) just as before.

After merge, one more thing is required by you, precious collaborator: npm publish

This pull request includes

• npm installation instructions in Readme.md
• brand new package.json, rewritten from component.json
• replacing require('emitter') by require('component-emitter') and similar as discussed in issue/41, providing compatibility for both component(1) and node/commonjs/browserify.
• removing remotes from component.json because the public component must not contain any remotes. If remotes exists, running component install produces error no remote found for dependency ....
• new builds of move.js and move.min.js, built with make move.js and make move.min.js. Apparently a few extra kilobytes were shaved off as well (28 kB -> 26 kB and 16 kB -> 14 kB).
• Version bumb to 0.5.0, because otherwise some 0.4.0 would work with npm and some would not.

After completing a move animation, the [-vendor]-transition-duration style is still on the element, which will alter other interactions outside of move.js. Current workaround is to remove it by passing callback to final end().

Perhaps the top-level end() should remove this style as part of move.js?

This adds the line to also clear the transition-duration alongside the transform and transition-property properties. It also calls applyProperties() which means the changes are actually made.

Added support and bridge for Ender. See my version of readme, 'integration/index.html', or let me know if you have questions.

If you accept these changes, please publish to npm.

Bashing a button to move an element takes the value as the element is clicked during the animation to add it to the value. A callback should be awaited

I'm experimenting with move.js, but on IE10, animations aren't visible at all. Check for example your demo page.

I don't know why move.js shouldn't run on IE10. Modernizr detects csstransforms and csstransitions.

Do you have more information?

I want a box to slide infinitely and i prefer doing it with move function directly, because the effect with css3 keyframe is crappy. But i didn't figure out a way to make move function run infinitely, is it possible?

Here is my code with move.js (the effect looks good):

function play(){
          var moveBack = move('.box')
              .x(0)
              .duration(10000);

              move('.box')
              .x(1000)
              .duration(10000)
              .then(moveBack)
              .end();

        }

And here is my code using CSS3 Keyframes (the effect looks crappy, but it runs inifinitely):

function play(){
          move('.box').animate('slide', {
            duration: '100s',
            'iteration-count': 'infinite'
          }).end();
        }

@-webkit-keyframes slide {  
        0% {  
          left: 0;
        }  

        50% {  
          left: 500px;
        } 
        100% {  
          left: 0;
        } 
      }

Right now, it's structured this way:

exports.Move = function Move() { ... }
Move.prototype.x = ...

This presents a problem as YUI compressor may mangle function Move() into a non-named function. We've encountered this problem using move.js with Jammit.

When calling "then", the transforms are being cloned. This results in the following code not functioning properly when run with the markup from /examples/transform.html.

move('#square').rotate(300).duration('2s').then().rotate(0).duration('1s').pop().end()

expected the square should transition to the 300 degree rotation over 2 seconds then return to 0 degree rotation over 1 second. actual the square transitions to 300 degree rotation over 2 seconds but the style property is set to rotate(300deg); rotate(0deg) when the 1s transition executes.

I have used move.js along with angular.js and trying to add some animations to newly added elements. when the elements are static it works fine.

Problem : Now,when i try to add the same to newly scope elements it doesn't apply.I guess there would be some issue with the sequence of execution. As the move.js functions functions runs before my angular js updates the scope method.

so far, i tried :+1:

1. Included it before body closing tag.
2. tried to get the regular jquery last element get function to identify the last element in the list(ie my newly added element) but it takes last but one element and applies my animations to that code.

Please let me know if i have any alternative or used any wrong approach.

Thank you in advance.

Hey there, if this isn't the place to post this, I apologise. I'm kind of a ~~rookie~~ intermediate js user, and I've been searching all over but haven't been successful at finding out just how would one go about using the easing.js extended effects lib together with move.js? Thanks in advance...

Added reflow method to simplify task of modifying style properties and immediately animating with those changes.

el.style.opacity = 0;

Move(el)
.reflow() //Reflows DOM element so animation will occur
.set('opacity', `)
.duration('1s')
.end();

Safari and Opera do not yet support scientific number notation in CSS. In JS, when very small numbers are converted to string, we usually end up with something like "-8.43858185037473e-19".

These unsupported number strings can reach this._transforms within Move.js, corrupting the resulting transformation.

For example, in my project, the following transformation string did not work in Safari 9.0.2:

"matrix(-8.43858185037473e-19, -0.003906249999999999, 0.003906249999999999, -8.43858185037473e-19, -1.3819999999999997 ,0.5000000000000001)"

There is some discussion how to prevent this.

I've got a few animations following one another. They work fine when I open the tab, however, when I open the tab in the background and switch to it later, I see that the animations overlap. After a few seconds, they "catch up".

Is this a known issue / something that has been observed before?

Failed to load the images from http://images.apple.com/ These examples include: move.js-master/examples/jquery.html move.js-master/examples/imac.html ect. You can check it in the download zip file named move.js-master.