25 messages in com.googlegroups.google-gadgets-apiRe: Sorry, this gadget uses the inlin...
FromSent OnAttachments
Matt (Guru)19 Dec 2007 09:03 
Matt (Guru)19 Dec 2007 09:08 
Dan (Google Employee)19 Dec 2007 10:10 
Matt (Guru)19 Dec 2007 11:53 
Dan (Google Employee)19 Dec 2007 12:29 
Matt (Guru)19 Dec 2007 12:42 
Dan (Google Employee)19 Dec 2007 14:01 
Bonstio (Guru)19 Dec 2007 14:48 
Bonstio (Guru)19 Dec 2007 15:02 
Jer...@EM19 Dec 2007 15:03 
cgmckeever19 Dec 2007 15:25 
Bonstio (Guru)19 Dec 2007 15:28 
mkco...@ccmaine.net21 Dec 2007 09:04 
Len21 Dec 2007 16:43 
prie...@gmail.com23 Dec 2007 14:10 
cgmckeever23 Dec 2007 16:15 
fhp...@gmail.com24 Dec 2007 09:30 
Jerome (Guru)24 Dec 2007 14:00 
Dan (Google Employee)02 Jan 2008 10:11 
cgmckeever02 Jan 2008 11:36 
Simon02 Jan 2008 12:35 
Dan (Google Employee)02 Jan 2008 15:53 
mark07 Jan 2008 19:31 
Bernie08 Jan 2008 14:31 
Jon Young25 Jan 2008 12:58 
Subject:Re: Sorry, this gadget uses the inlining feature, which is no longer supported.
From:Bonstio (Guru) (bons@gmail.com)
Date:12/19/2007 02:48:37 PM
List:com.googlegroups.google-gadgets-api

People have now started reporting this problem with my Custom iGoogle Skins gadget. I have multiple URLs for this gadget and am trying to figure which ones are affected. It has not affected me... yet.

On Dec 19, 10:01 pm, "Dan (Google Employee)" <api.@google.com> wrote:

Hi Matt,

I was also under the impression that type="html" was the default, but I wanted to eliminate that as a variable in this process (since perhaps the inline deprecator would flag anything without a specified content type). I will pass your information about the all-lower case vs. upper-and-lower case URLs along.

Thanks, Dan

On Dec 19, 12:42 pm, "Matt (Guru)" <m.@mattkruse.com> wrote:

On Dec 19, 2:29 pm, "Dan (Google Employee)" <api.@google.com> wrote:

It looks like the last
onehttp://www.javascripttoolbox.com/gadget/superdigg/superdigg.xml is missing a content type attribute. I don't know specifically whether this is causing the problem, but it could be.

I tried putting type="html" in the <Content> and it made no difference. My assumption has always been that this was the default, and other gadgets I've written have omitted the type attribute without any problems, but I will make sure to add it going forward.