Side navigation
#3291 closed bug (invalid)
Opened August 26, 2008 09:03AM UTC
Closed August 28, 2008 02:22PM UTC
Error with value == NaN
Reported by: | Dr4g0nF1y | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 1.3 |
Component: | core | Version: | 1.2.6 |
Keywords: | Cc: | Dr4g0nF1y, flesler | |
Blocked by: | Blocking: |
Description
Attachments (2)
Change History (9)
Changed August 26, 2008 06:12PM UTC by comment:1
cc: | → Dr4g0nF1y, flesler |
---|---|
need: | Review → Test Case |
Changed August 26, 2008 06:12PM UTC by comment:2
priority: | blocker → minor |
---|
Changed August 27, 2008 06:45AM UTC by comment:3
Replying to [comment:2 flesler]:
I considered this error a blocker since it runs my website in IE useless.
Although I didn't use things I shouldn't or couldn't use. In FF it runs like a charm, but in IE I get an error that the action I want to run is not supported by the object.
After that I get an runtime error that is thrown at the code above. Checking wether the value is NaN and thus a getter instead of a setter, does not help.
Changed August 27, 2008 03:06PM UTC by comment:4
The priority is in relation to the framework, not to your personal work.
Will try to check the test case as soon as I can.
Thanks
Changed August 27, 2008 03:08PM UTC by comment:5
you can test here. it's the page that jams in IE
Changed August 28, 2008 07:03AM UTC by comment:6
By using the microsoft script debugger, I found the culprit... it's an jQuery Plugin called "jMyCarousel".
If you have MSD, follow the callstack, and you'll see it.
Somewhere between the call for the "getcontent" and the error, the value of the function -which produces the error- get's to NaN.
Changed August 28, 2008 01:57PM UTC by comment:7
Then how come the 2nd js file attached doesn't call the plugin and you still mention an error ?
That means error.js doesn't trigger any error ?
Changed August 28, 2008 02:09PM UTC by comment:8
Replying to [comment:7 flesler]:
Then how come the 2nd js file attached doesn't call the plugin and you still mention an error ? That means error.js doesn't trigger any error ?
That is because it is called in the first file. And at the time I didn't know that it was the plugin that caused the error.
But I guess that should be obvious. I understand that a smaller file is advised/prefered, but since not everyone can actually find the error, a little effort for the bigger file (or a request of the issueing url) is not useless.
I have rebuild my Internet Explorer version of the script, and thus can this ticket be closed. Not to my satisfaction, but that is not the cause of jQuery or it's developers but a 3rd party.
I thank you (all) for your time and effort.
Changed August 28, 2008 02:22PM UTC by comment:9
resolution: | → invalid |
---|---|
status: | new → closed |
Ok, thanks.
Can you please provide a test case ? that is, a small html file with the minimum html/css/js necessary to reproduce the problem.
Please keep it simple, the js you provide is way too long.