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 On Apr 15, 3:47 am, CG <[email protected]> wrote: > By now, I traced the problems described yesterday to a conflict > between prototype.js and the current gadget API. In a very simple test > gadget, basic API calls like gadgets.window.adjustHeight() will cease > to work if prototype.js is included. The actual gadget in question was > developed using the prototype library, which has not been a problem > for years. Something within the gadget API must have changed a few > days ago, causing the conflict. Anyone having similar problems? Any > chance to solve this without a complete re-write of our gadget? -- 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.
