On 2008-04-12, at 15:57 EDT, André Bargull wrote:
I found out what's happening:
Arithmetics are a bit different in both runtimes:
DHTML: null / 100 = 0
SWF: null / 100 = NaN
So in swf, the slider's value gets set to "NaN", that's why it is
endless recursing as "NaN != NaN" always evaluates to true.
(Actually, when I type into the debugger in swf: "NaN != NaN" it
evaluates to "false", but if I use: "0/0 != 0/0", I get the right
result, therefore "true". Does anybody know what's happening here?)
The swf runtime is broken. The ECMA spec says Number(void 0) -> NaN,
Number(null) -> 0. SWF has this wrong. We have several NaN tests
turned off in lzunit for SWF because of these bugs. I suppose we
should report this (possibly again) to Adobe.