Ticket #10942 (closed bug: invalid)
Make a version of isNumeric() that is compatible with parse[Int|Float]
| Reported by: | jdmarshall | Owned by: | jdmarshall |
|---|---|---|---|
| Priority: | undecided | Milestone: | None |
| Component: | unfiled | Version: | 1.7.1 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
Several bugs related to data() and large numbers have been dismissed as won't fix, duplicates, or wrong characterization. For example, Ticket #10856
The resolution states that these numbers ARE numeric, and they can be converted. However, converted while chopping off significant figures can't really be considered a success.
It would be better I think to have a function similar to isNumeric() but that only returns true when the number can be successfully converted into the appropriate Javascript data type. Then the spots that do this conversion should use that version.
Change History
comment:1 Changed 18 months ago by dmethvin
- Owner set to jdmarshall
- Status changed from new to pending
comment:2 Changed 17 months ago by trac-o-bot
- Status changed from pending to closed
- Resolution set to invalid
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
Can you explain the use case for this new version, preferably in the form of a jsFiddle.net page that demonstrates the problem?