What steps will reproduce the problem?
I was unable to reproduce with your live demo, only within our app. Could
be environmental(?)
What is the expected output? What do you see instead?
Expected to return a Date object, consistently get NaN instead.
For whatever reason this method always returns NaN only in IE6 and only in
our production app. However, calling new Date(string) inline instead of
using Date.parseFormattedString works fine. What is the purpose of this
abstraction? It seems as though it's only used once in the script. I see no
reason why we can't call new Date(string) directly. Thoughts?
For the time being to correct our issue, I will call new Date instead.
Thanks!
Original issue reported on code.google.com by g...@joefiorini.com on 16 Dec 2008 at 9:19
Original issue reported on code.google.com by
g...@joefiorini.com
on 16 Dec 2008 at 9:19