I'm on the Chrome Extensions team, and we've run into a problem where extensions override Array.prototype.forEach in a way that breaks our internal JS.
A workaround we've done is to write our own forEach method, but this problem is widespread - extensions also override JSON, document.createElement, etc - the vector for accidental breakage is as widespread as all of the JS and DOM libraries. What is the best way to protect against this in a general way? The only safe thing I can think of is to run all our code in a separate context, but I've been told that creating contexts is an expensive operation. How expensive? Alternatively, apparently v8 has solved this problem internally by guaranteeing that it's running the builtin libraries - is/can this be exposed? Cheers, Ben. -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
