I did a quick Markmail and opensocial.org search, and found lots of discussions, proposals and even +1 votes. But where it counts, the v0.9 spec, and errata proposal for v1.0, there is nothing. So as it stands, the official OpenSocial container MUST render in quirks mode. Anything Shindig does with options is a Shindig only extension. Also, I seem to recall some other production containers NOT rendering in quirks mode.
Did something really get adopted for the spec and simply not properly incorporated in the docs? Or something else? BTW - some of the people on this email thread were also on the other threads of discussion. -----Original Message----- From: John Hjelmstad [mailto:[email protected]] Sent: Tuesday, October 27, 2009 6:52 PM To: [email protected] Subject: Re: HTML doctype declaration for content I seem to recall that the decision we made a while back was: * if no doctype specified, let default reign (quirks, equivalent to writing a doctype-free webpage) * else include doctype Take that with a grain of salt; it's been a while. Perhaps it's worth plumbing the archives for the longer discussion. --j On Tue, Oct 27, 2009 at 6:35 PM, Chirag Shah <[email protected]> wrote: > Hey, > > It looks like there's a discrepancy in which HTML doctype is used > between the Java and PHP gadget renderers. > > GadgetHtmlRenderer.php says that "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD > HTML 4.01//EN\" \"http://www.w3.org/TR/html4/strict.dtd\";>" should be > used when "quirks = false or empty in the view." > > The Java Gadget renderer will not set a default doctype if it can't > find one. Shouldn't both systems explicitly set a doctype if it's not > provided? >
