> Is this expected behaviour? HTMLSerializer does output a > valid HTML file. If XHTML is intented for "correcting" lousy > html, isn't it resonable to output a valid html?
XHTML is a valid XML document that uses elements originally defined for HTML. Therefore it must be a valid XML document first. The way some (most?) browsers work, a valid XHTML document may not be a valid HTML document. This is mostly a problem with script and style which have a special handling in HTMLSerializer. XHTMLSerializer forces them to conform to the XML document encoding. arkin > > Thanks, > Zhaohua Meng > > Hotlens.com Inc. > http://www.hotlens.com > > 350 Fifth AVE > Suite 3113 > New York, NY 10118 > Phone: 212-465-1700 > Fax: 212-465-1710 > email: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- ---------------------------------------------------------------------- Assaf Arkin [EMAIL PROTECTED] CTO, Intalio Inc. www.intalio.com The Business Process Management Company (650) 345 2777 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
