[Seaside] XHTML

[Eric Hodel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Jun 25, 2004, at 6:00 PM, Avi Bryant wrote:

> Given that there's been ongoing discussion (both on and off list) 
> about Seaside's XHTML compliance, I thought the below was interesting. 
>  It's from the WHATWG mailing list (see http://www.whatwg.org).  Dave 
> Hyatt is the development lead on Safari.
>
> Has anyone noticed this affecting anything in practice?  Are we better 
> to output HTML4 Transitional for now, and flip the XHTML switch once 
> browser support improves?

Problems may occur if you send a MIME type of application/xhtml+xml 
instead of text/html.  There would be no problem in sending HTML4 or 
XHTML1.0 (XHTML1.1 may be sent as text/html, but should be sent with an 
XML mime type).  I think it would be fine to send XHTML1.0 as 
text/html, and provide a hook to switch to an XHTML mime type.  
Provided you follow XHTML1.0's appendix C (HTML compatibility) nobody 
should notice any problems.

- -- 
Eric Hodel - drbrain at segment7.net - http://segment7.net
All messages signed with fingerprint:
FEC2 57F1 D465 EB15 5D6E  7C11 332A 551C 796C 9F04

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFA3crLMypVHHlsnwQRAsYiAJ4lJ9HzSdb9F045egxY6oSn58esfQCg+Zn6
+7sBa2sf0RdW47sM8C0Xby0=
=gSOw
-----END PGP SIGNATURE-----