I've never met a browser not understanding String.substr() properly. I've been using this method for 5 years without any problems what so ever?!

There may not be problems with it in current browsers, but if there’s a standard, fully specced method (and there are several options here) why not use that one?

Edit: Just to be clear: this was just a friendly heads up, I don’t mean to start a flamewar here.

No no no flamewar going on here! I'm just surprised by your intel.
Go ahead and replace those .substr() by whatever you seem fit. I'll be happy to merge…
(heading out to a meeting now ☹)

https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/String/substr says substr() has been around since Javascript 1.0, although no ECMA specification. I wonder if this really is an issue :/

I wonder if this really is an issue :/

It’s not — it’s just good practice to use standardized methods where possible.

I don't disagree. I find it interesting, though, that both standardized methods slice() and substring() take an index as the end-point, rather then number of characters to read (like substr() in any other language I know does…). weird.

Fixed in v1.1.0