You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was testing out an implementation of the time picker with some new code -- when my firebug blew up with error messages (alignValue.toFixed is not a function) while sliding the minute field.
The site is using jQuery ui 1.8.17 and jQuery 1.6.4 -- running Firefox 12 on Ubuntu 12.04.
Anyways, after a quick search I came upon this thread (http://forum.jquery.com/topic/alignvalue-tofixed-is-not-a-function) in the jQuery forums. As suggested, I wrapped each value (value, min, max, step) within the slider function (line numbers: 469, 484, 496, 508, 768, 770, 772, 774) with parseFloat().. This seems to have corrected this issue.
I'm pretty busy atm.. so I haven't had a chance to look at an optimization (primarily, to see where adding parseFloat is necessary and where it is not), to test other versions / combinations of jQuery, jQuery UI, etc.... and to obviously push these suggested changes.. in the meantime, if someone else has a chance to look at this, can confirm it.. or just stumbles upon it from a web search.... great :)
The text was updated successfully, but these errors were encountered:
I was testing out an implementation of the time picker with some new code -- when my firebug blew up with error messages (alignValue.toFixed is not a function) while sliding the minute field.
The site is using jQuery ui 1.8.17 and jQuery 1.6.4 -- running Firefox 12 on Ubuntu 12.04.
Anyways, after a quick search I came upon this thread (http://forum.jquery.com/topic/alignvalue-tofixed-is-not-a-function) in the jQuery forums. As suggested, I wrapped each value (value, min, max, step) within the slider function (line numbers: 469, 484, 496, 508, 768, 770, 772, 774) with parseFloat().. This seems to have corrected this issue.
I'm pretty busy atm.. so I haven't had a chance to look at an optimization (primarily, to see where adding parseFloat is necessary and where it is not), to test other versions / combinations of jQuery, jQuery UI, etc.... and to obviously push these suggested changes.. in the meantime, if someone else has a chance to look at this, can confirm it.. or just stumbles upon it from a web search.... great :)
The text was updated successfully, but these errors were encountered: