> Add this code after prototype.js =) Thus far, this is the technique we've already been advocating, though in considerably shorter form. It's a stop-gap measure at best, and brittle at worst. However, my issue here is that while we're waiting for a newer version of Prototype, more sites are deploying the current version, and every time they do, that's one more site that's now incompatible with some of our APIs. Plus, there's not exactly an auto-update feature for JavaScript libraries. For every user that contacts our support team (and hopefully, gets correctly diagnosed and given a fix) there are ten more that give up before even talking to support. Of those ten users, most will assume the problem is Google's fault, because the visible breakage happens in our code even though the bug is Prototype's. I'm happy to contribute patches or do whatever you guys need to make this fix happen.
-Bob Aman -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en
