On Fri, Feb 08, 2008 at 07:36:57PM -0800, Kevin Brown wrote: > Unfortunately, Quirks mode is required by the spec. See Item 6 under > "Compliance" at http://code.google.com/apis/gadgets/docs/spec.html.
That's really unfortunate. Right now you have a great opportunity to
make a clean break towards standards mode. People are going to be
rewriting their Apps for Caja, plus they'll be customizing UI etal for
each new platform.
> This issue has been brought up numerous times in the past, but there hasn't
> been a resolution on it yet. The only reason for this is that many (if not
> all) existing gadgets have to be updated to use standards mode since the
> original iGoogle site used quirks mode.
Where are these discussions taking place? Internal to Google I assume?
Has anyone actually tried, say the top 100 apps rendered in standards
mode? I really doubt that it's that much of a problem.
> Many people (myself included) have attempted to move it towards
> standards mode, but so far nobody's come up with a viable solution
> for backwards compatibility.
How about this:
* Always render iGoogle gadgets using legacy gmodules.com.
* New widgets (those using opensocial or other new technologies) will
be sent through a Shindig based server.
* Mark quirks mode deprecated with a sunset of 1 year from now.
Alternate solutions:
1. If Gadget XML contains proper xmlns namespace then use standards
mode, other wise quirks mode
<Module xmlns:gadget="http://shindig.apache.org/ns/0";>
2. Allow developer to specify rendering at the top of the Gadgets
XML..
<?xml ... ?>
....declaration goes here ....
We should really try to fix this problem if we can.
--
Paul Lindner
hi5 Architect
[EMAIL PROTECTED]
pgpKeGdn3K6ro.pgp
Description: PGP signature
