it was just a heads-up really – if you do

parseInt("0034")

for example, you'll get 28 as a result, whereas if you do

parseInt("0089")

you'll get either 0 or NaN.

In browsers which support ECMAScript 5, which is basically just Chrome at the moment,  this silly behaviour is removed and parseInt works how you'd expect. Still, best to be on the safe side.