Timeline does not work correctly at millisecond scale on IE about chap-links-library HOT 9 CLOSED

I've had feedback from a user that the same is true of IE9 as well - can't verify directly at the moment.

from chap-links-library.

It seems to be the case on on versions of Internet Explorer, I tested on IE8 and IE9.

from chap-links-library.

Yes - sorry - I posted before I saw your update on Google Groups!. Out of interest, is github your preferred 'focus' for this kind of thing?

from chap-links-library.

I think Github should be used for version control of the code, issue tracking, and feature requests. And the Google Groups is better suited for discussion, questions, and sharing of ideas.

from chap-links-library.

OK, makes sense.

Regarding this bug on IE - I'm happy to have a go at finding the cause / solution, but I'm really only familiar with Firebug on FF. Any advice where to start with IE (either from the dev tool side, or from the Timeline library side - e.g., do you have a suspicion as to where it's likely to be)? You mentioned non-integer date values on the google group - does that mean they need to be managed as integers throughout the code, or just in specific places?

Thanks,

Dave.

from chap-links-library.

I guess you will have to do with the developer tools built in in IE, though I'm no IE expert. It is quite doable in IE9: it allows you to set debug points and output to the console, watch variables, test in IE7-IE9 mode, etc.

from chap-links-library.

I managed to make some headway in IE8 (I have to stick with WinXP for now, so IE9 is not possible). Not sure I've got to the source yet, but there's definitely something strange going on in .onMouseDown. I've set up a dummy timeline at the millisecond scale with a few events on it, and at line 2850 an error is thrown:

        dom.items.frame.style.left = (frameLeft) + "px";

frameLeft is '-infinity' on IE, and 25 on FF. Tracking back, it seems that IE can't cope with a start value of 0 (i.e. 1/1/1970), and it quickly gets confused and sets 'interval' at line 2823 to 0, resulting in a division by zero later on.

Re your google group comment, I can't see any fractional values being used - they all seems to be integers. I'll keep digging.

from chap-links-library.

This issue now seems to affect Firefox as well in FF17.0.1. (I'm not sure the cause is the same, but the observed symptoms are identical.)

If you need me to run a test or two, drop me a line.

from chap-links-library.

thanks. It's indeed showing up on different browsers. I guess it is an obvious bug once found, but we haven't yet taken the time to figure it out.

from chap-links-library.