I've reproduced this with Prototype 1.6.0.2 on Firefox 3.6. It doesn't happen on all browsers though, IE8 appears to be unaffected for example. I've made the team aware of the issue and I've filed it on the tracker at http://code.google.com/p/igoogle-developers/issues/detail?id=6 .
Rob Russell Google Developer Relations On Fri, Apr 16, 2010 at 11:12 AM, Michael Geary <[email protected]> wrote: > What version of Prototype.js are you using? > > Your earlier comment that Prototype "has not been a problem for years" > makes me think you may be running a very old version, one that extends > Object.prototype - which breaks all sorts of other code. > > Newer versions of Prototype no longer extend Object.prototype. You can > search the Prototype.js source code for Object.prototype or check the > version number. > > -Mike > > > On Fri, Apr 16, 2010 at 12:24 AM, CG <[email protected]>wrote: > >> Hi Justin, >> >> Thanks for your reply. Actually, the simple hello-world-gadget I wrote >> to trace this bug was type="html" and it's displaying the same >> symptoms. The test gadget isn't even *using* prototype.js. Just >> loading it causes adjustHeight() to stop working for me. I'm trying to >> strip down prototype.js now, removing all the parts that aren't >> absolutely essential to our gadget. Mostly, this will be the >> inheritance-part and I'm planning to use jQuery for the rest. Seems >> like it's going to work but of course it's quite an effort. >> >> -Christian >> >> On 15 Apr., 15:59, SerranoABQ <[email protected]> wrote: >> > I noticed this too while working with mootools (which is sort of >> > based on Prototype) in a type="url" gadget. I saw exactly what >> > you described--calls to prefs.set and adjustHeight() suddenly >> > stopped working. I'm not sure what's causing it, but in my >> > gadget I was able to trace it to the JSON portion of the mootools >> > core. It seems that the prefs.set and adjustHeight calls use >> > Google's own JSON implementation, which conflicts with the one >> > used by mootols (or prototype). I'm not familiar with prototype.js, >> > but if you can exclude all JSON-related code from it (in mootools >> > you can), your gadget should work again as it did for me. >> > >> > I'd like for Google to give an official reply on this, because it >> > is a real headache to have a fully developed gadget stop functioning >> > because of some seemingly random code change. Especially one as >> > difficult to trace as this one. >> > >> > -Justin >> >> -- >> You received this message because you are subscribed to the Google Groups >> "iGoogle Developer Forum" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<google-gadgets-api%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/Google-Gadgets-API?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "iGoogle Developer Forum" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-gadgets-api%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/Google-Gadgets-API?hl=en. > -- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
