Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In this font-size resizing tutorial:
the author uses parseFloat with a second argument, which I read here:
Is supposed to specify the base of the supplied number-as-string, so that you can feed it ‘0x10’ and have it recognized as HEX by putting 16 as the second argument.
The thing is, no browser I’ve tested seems to do this.
Are these guys getting confused with Java?
No, they’re getting confused with
parseInt(), which can take a radix parameter.parseFloat(), on the other hand, only accepts decimals. It might just be for consistency, as you should always pass a radix parameter toparseInt()because it can treat numbers like010as octal, giving8rather than the correct10.Here’s the reference for
parseFloat(), versusparseInt().