Preliminary tests seems to point the finger at the Tabs library in combination with the gadgets.* API. Will have to run some more tests before posting a bug report.
On Dec 6, 7:51 am, nicky <[email protected]> wrote: > Hi Mike, > > I think the best thing to do would be to file an issue here: > > http://code.google.com/p/igoogle-developers/wiki/IssuesTab?tm=3 > > The problem seems to be linked to gadgets.io.makeRequest, although I'm > really not sure. It's disappointing to see an empty/almost empty > preview pane, especially when a gadget actually works when added to a > webpage. > > There's a couple more references to the problem > here:http://groups.google.com/group/Google-Gadgets-API/browse_thread/threa...http://groups.google.com/group/Google-Gadgets-API/browse_thread/threa... > > On Dec 4, 4:44 am, mike <[email protected]> wrote: > > > On Dec 3, 10:22 pm, mike <[email protected]> wrote: > > > > As reported last year <http://goo.gl/HmXb6>, the "Add this gadget to > > > your webpage" page does not play well with the gadgets.* api. Though > > > the generated code works (either with the /ig/ or /gadgets/ in the > > > URL), users see an empty preview frame and abandon the creator page. > > > The creator page with gadget in question can be seen at <http://goo.gl/ > > > djlfr>. > > > Correcting above link ...<http://goo.gl/djlfr> > > > > Is google addressing this? Is there something I can do in my gadget > > > to resolve this (besides going back to the legacy api)? Am I just > > > missing some important piece of info here? > > > > Thanks. -- 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.
