> I have Chrome 4 and it's not throwing any errors - so if there was an > issue with 3, it's gone in 4 - (what OS are you using? I'm on XP, I'll > check the OSX later)
It's XP, Chrome 3 very latest stable. I tried the Chrome 4 Beta elsewhere and you're right, no bug there. Based on glancing at their trunk, I think they've now namespaced it as goog.bind only, instead of also touching Function.prototype.bind. It is interesting that these functions exist -- though their source language is JS, I'm assuming they are compiled or somehow optimized when Chrome starts? Wonder if detecting + using these could be faster than using the Moo varieties? Yes, you would be embracing non-standard stuff, even if such helper functions have become "framework-standard"; and already we see a Moo-familiar function name but a Moo-unfamiliar signature. I dunno. -- Sandy
