Fix for Safari 6 toString() defaultFormatter bug #472

Closed
wants to merge 1 commit into
from

Projects

None yet

5 participants

@jaywilliams

On Safari 6 in Lion, the toString() method will fail with the message TypeError: Type error when parsing certain numeric data if the Error Console is not open. If the Error Console is open, the error does not occur. This bug doesn't occur in Safari 5.

Due to the strangeness of this bug, I'm assuming it's browser specific. To get around this bug, I used string concatenation, rather than the toString() method.

@jaywilliams jaywilliams Fix Safari 6 toString() defaultFormatter() bug
On Safari 6 in Lion, the toString() method will fail on numeric data if
the Error Console is not open. By using string concatenation, this gets
around this strange Safari bug.
6b8de21
@pake007

Thanks for the commit!

I also meet this problem.

@blicksky

I found that simply wrapping the toString() call in a try/catch block seems to have the same effect as opening the error console or developer tools, and seems to avoid the issue.

@Olegas
Olegas commented Apr 30, 2013

@jaywilliams I've expiriencing this bug on mobile Safari on iOS. Can you reproduce it with some "localized" code, not in a real app?
Trying to reproduce too, but failed for now. Reproduced not stable only in my app/site (not related to SlickGrid).

@mleibman
Owner

Merged in e016c9f

@mleibman mleibman closed this Apr 30, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment