[Seaside] XHTML

Julian Fitzell julian at beta4.com
Sat Jun 26 09:17:13 CEST 2004


We need to at least make it configurable if you want to take awa XHTML. 
  We need XHTML output to fit into the uPortal channels at work, for 
example.

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?
> 
> Begin forwarded message:
> 
>> From: David Hyatt <hyatt at apple.com>
>> Date: June 25, 2004 5:50:23 PM PDT
>> To: Ian Hickson <ian at hixie.ch>
>> Cc: whatwg-whatwg.org at lists.whatwg.org, Jim Ley <jim.ley at gmail.com>
>> Subject: Re: [whatwg] Re: Is this introducing incompatibilities with 
>> future W3C work
>>
>> This is actually not quite true.  There are a number of features that 
>> don't "just work" when you make a switchover to XML, and in fact the 
>> set is so non-trivial that I don't think you should gloss over this so 
>> readily.  In general both Mozilla and Safari's application/xml+xhtml 
>> support lags substantially behind their text/html support.  Neither 
>> browser can even render XHTML incrementally for example (last time I 
>> checked at least).
>>
>> Some other examples are features like .innerHTML, DOM serialization, 
>> and contenteditable.  HTML elements have all sorts of situations where 
>> code that is written to handle HTML streams or HTML editing concepts 
>> has to change to deal with XML streams etc.
> 
> 
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside


More information about the Seaside mailing list