Right, I don't see a reason to do that, though — it doesn't buy us anything.<br><br>The reason the HTML5 doctype is simply:<br><span style="font-family: Arial,sans-serif; font-size: 16px;"><pre><font face="Helvetica" size="3"><span style="font-size: 12px;"><!DOCTYPE html></span></font></pre>
</span>…is that it's the shortest possible string that will trigger strict/standards parsing (ie. not quirks mode) in all browsers, including IE6.<br><br><br><div class="gmail_quote">On Tue, Mar 16, 2010 at 3:34 PM, Laurence Rowe <span dir="ltr"><<a href="mailto:l@lrowe.co.uk">l@lrowe.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">It is listed as an "obsolete permitted doctype string"<br>
<div class="im"><a href="http://dev.w3.org/html5/spec/Overview.html#obsolete-permitted-doctype-string" target="_blank">http://dev.w3.org/html5/spec/Overview.html#obsolete-permitted-doctype-string</a><br>
</div>- i.e. we can lie about the doctype. I'm not sure why xhtml 1.0<br>
transitional is not allowed.<br>
<font color="#888888"><br>
Laurence<br>
</font><div><div></div><div class="h5"><br>
On 16 March 2010 22:18, Alexander Limi <<a href="mailto:limi@plone.org">limi@plone.org</a>> wrote:<br>
> The way it works is that you can use the XHTML "spelling" (ie. closing your<br>
> tags), but you serve it up as normal HTML.<br>
><br>
> <a href="http://wiki.whatwg.org/wiki/FAQ#Should_I_close_empty_elements_with_.2F.3E_or_.3E.3F" target="_blank">http://wiki.whatwg.org/wiki/FAQ#Should_I_close_empty_elements_with_.2F.3E_or_.3E.3F</a><br>
><br>
> There's no Strict or similar thing in HTML5, AFAIK.<br>
><br>
> (There is also something informally referred to as "XHTML5" which is serving<br>
> it as XML, which isn't what we want to do)<br>
><br>
> On Tue, Mar 16, 2010 at 3:06 PM, Laurence Rowe <<a href="mailto:l@lrowe.co.uk">l@lrowe.co.uk</a>> wrote:<br>
>><br>
>> By my reading of the html 5 draft, it would seem conformant with the<br>
>> (html5) spec to serve a document with a text/html Content-Type but an<br>
>> XHTML Strict doctype.<br>
>><br>
>> On 16 March 2010 20:14, Alexander Limi <<a href="mailto:limi@plone.org">limi@plone.org</a>> wrote:<br>
>> > What does transitional doctype have to do with geolocation?<br>
>> ><br>
>> > (and XHTML STRICT is a problem, since it implies serving with XML MIME<br>
>> > type,<br>
>> > which IE doesn't handle, so that's unlikely to happen)<br>
>> ><br>
>> ><br>
>> > On Tue, Mar 16, 2010 at 12:48 PM, Veda Williams <<a href="mailto:veda@groundwire.org">veda@groundwire.org</a>><br>
>> > wrote:<br>
>> >><br>
>> >> This brings up the question of when we're moving away from Transitional<br>
>> >> DOCTYPE. Do we have a sense of when this will happen? I'm particularly<br>
>> >> keen<br>
>> >> on knowing, as it opens up the door for us in terms of geolocation in<br>
>> >> the<br>
>> >> next year or so.<br>
>> >> Thanks,<br>
>> >> - Veda<br>
>> >><br>
>> >><br>
>> >> On Mar 16, 2010, at 12:40 PM, Alexander Limi wrote:<br>
>> >><br>
>> >> On Tue, Mar 16, 2010 at 4:45 AM, Wichert Akkerman <<a href="mailto:wichert@wiggy.net">wichert@wiggy.net</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>> I'ld like to see a list of pros and cons of using HTML 5 as well. I am<br>
>> >>> quite worried by the lack of proper support in existing browsers. None<br>
>> >>> of<br>
>> >>> them implement any of the existing HTML standards properly, and I fear<br>
>> >>> that<br>
>> >>> switching to the still unfinished HTML5 would be a several steps too<br>
>> >>> far at<br>
>> >>> this point in time.<br>
>> >><br>
>> >> What parts in particular do you find are not working? Browsers that<br>
>> >> don't<br>
>> >> have dedicated support for HTML5 will just treat those tags similar to<br>
>> >> div<br>
>> >> elements (given an HTML5 shiv for styling to apply in IE), and most of<br>
>> >> the<br>
>> >> new form-related enhancements are additive in nature.<br>
>> >><br>
>> >> In general, HTML5 renders even on IE6, there isn't much magic here (but<br>
>> >> of<br>
>> >> course it doesn't get any of the advantages either). HTML5 is mostly<br>
>> >> about<br>
>> >> standardizing edge case behaviors and adding new abilities that will<br>
>> >> gracefully degrade in older browsers — and then a few new tags like<br>
>> >> video/audio (that are also relatively easy to make degrade) and<br>
>> >> structural<br>
>> >> elements like article/footer, etc.<br>
>> >><br>
>> >> --<br>
>> >> Alexander Limi · <a href="http://limi.net" target="_blank">http://limi.net</a><br>
>> >> _______________________________________________<br>
>> >> Framework-Team mailing list<br>
>> >> <a href="mailto:Framework-Team@lists.plone.org">Framework-Team@lists.plone.org</a><br>
>> >> <a href="http://lists.plone.org/mailman/listinfo/framework-team" target="_blank">http://lists.plone.org/mailman/listinfo/framework-team</a><br>
>> >><br>
>> >> ________________________________<br>
>> >> Veda Williams<br>
>> >> Web Developer<br>
>> >> Groundwire<br>
>> >> 206.286.1235x23<br>
>> >> <a href="mailto:veda@groundwire.org">veda@groundwire.org</a><br>
>> >> ________________________________<br>
>> >> ONE/Northwest is now Groundwire! Read all about our new name.<br>
>> ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > Alexander Limi · <a href="http://limi.net" target="_blank">http://limi.net</a><br>
>> ><br>
>> > _______________________________________________<br>
>> > Framework-Team mailing list<br>
>> > <a href="mailto:Framework-Team@lists.plone.org">Framework-Team@lists.plone.org</a><br>
>> > <a href="http://lists.plone.org/mailman/listinfo/framework-team" target="_blank">http://lists.plone.org/mailman/listinfo/framework-team</a><br>
>> ><br>
>> ><br>
><br>
><br>
><br>
> --<br>
> Alexander Limi · <a href="http://limi.net" target="_blank">http://limi.net</a><br>
><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Alexander Limi · <a href="http://limi.net">http://limi.net</a><br>