uncaught exception: [Exception... "Not enough arguments" nsresult: "0x80570001

[bluntworks]

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]

[tj]

it's a little broken in non-webkit browsers ATM sorry

[bluntworks]

No Problem Tj, really like it.

Having another issue in chrome probably something stupid i'm doing trying to run

this code on document load

move('.Obj')
.duration(5000)
.x(100).y(200)
.end();

.Obj is positioned absolute etc but it just sets the position to those coordinates no actual animation, ie its instantaneous, also same thing happens if i trigger it from a click event.

cheers Dave

[tj]

hmm looks fine at a glance

[bluntworks]

ok figured it out, If I have a doctype in the page it doesnt seem to work neither html 5 or html 4 or atleaset the doc types produced by jade for
!!!
and
!!!5

If I take the doctypeout alltogther it works fine

[tj]

hmm that's interesting, never heard of that affecting js

[bluntworks]

yup very strange, just tried it on some of move.js examples directly (instead of loading through node/express/jade) and setting the doctype on any of them seems to stop any animation.

can you recreate the issue or is this something specific my system windows xp & chrome 11.0.696.68

no errors showing up in inspector/console either

[tj]

hmm yeah definitely same for me

[tj]

interesting, it works in safari fine, figured it might be camel-casing of the props or something

[bluntworks]

Hi TJ,

The issue seems to be to do with setting the transition-duration property by default you are setting to 500 however if you set to "1s" or ".5s" it works fine (with doctype etc) also if you add a third parameter to style.setProperty of an empty string

el.style.setProperty(prop, props[prop],'');

it fixes the original uncaught exception issue for firefox

cheers _dR

[tj]

interesting, without the doctype 500 etc is fine for ms, however with the doctype when I append 'ms' things are fine but it doesn't like the literal haha... very... odd. Some of the other examples are failing with a doctype as well, looking into it

[tj]

actually it's probably the same issue, 100 vs 100px

[tj]

yup

[tj]

closeddd