I am wondering if they did some magic on the server to return the right iframe. Maybe Paul could provide some insight.
On Wed, Oct 2, 2013 at 7:20 PM, Stanton Sievers <siever...@gmail.com> wrote: > Hi Darren, > > For the modules that state that they are built-in, like weather and gmail, > iGoogle is bypassing parts of Shindig and loading an iframe pointing > directly to their content. You can see this if you use an HTML inspector > on iGoogle look at Gmail. Its iframe's src attribute points directly to > gmail instead of to a Shindig server, e.g., > https://mail.google.com/mail/ig/mailhome?hl=en&gl=us... > > If you look at some of the other gadgets, like this translator gadget [1], > you'll see it is using Shindig as its iframe's src attribute indicates: > http://www-ig-opensocial.googleusercontent.com/gadgets/ifr... > > I can't think of a way in which you could handle this easily. On the > client-side, Google has ignored the iframeurl that is returned by Shindig > and are using their own. And I don't see any information in the gadget XML > itself that indicates what URL they plan on using, so I'm not sure how they > are generating that data. > > [1] http://www.gstatic.com/ig/modules/dictionary/dictionary_v2.xml > > -Stanton > > > On Wed, Oct 2, 2013 at 7:44 AM, Darren Bond <db...@globalcad.com> wrote: > >> Dear All, >> >> Within the description of some gadgets there appears to be no real content >> within the <Content type="html"> tag of the gadget's specification. An >> example of this is the Weather gadget... >> >> http://www.google.com/ig/directory?type=gadgets&url=www.google.com/ig/module >> s/builtin_weather.xml >> http://www.google.com/ig/modules/builtin_weather.xml >> How should we operate and handle such gadgets? >> >> The following test site highlights the issue:- >> http://beta.blueg.com/test/personal.htm >> >> Kind regards, >> >> Darren >> >>
