On Sun, Jul 26, 2009 at 4:58 PM, Craig Andrews<[email protected]> wrote: > I ran across an interesting bug where WebKit throws an exception when > invalid XHTML (but, notably valid HTML) is written to the DOM using > javascript. The problem is that oohembed.com returns valid HTML, but > invalid XHTML, for youtube urls. When laconica creates the jOverlay, > invalid markup is written to the DOM, so the browser throws an error. This > effects all webkit browsers, including Safari, Midori, Chrome, etc > > http://laconi.ca/trac/ticket/1734 is the bug - I have a more detailed > explanation there. > > If we return the content-type as "text/html" instead of "application/xml" > or "application/xhtml+xml" webkit works fine, as laconica is now writing > valid markup to the DOM. > > I suggest laconica stop serving xhtml mime types, and only serve > "text/html" for web pages.
Could we instead do some translation of the offending html into valid xhtml? The nice part of having browsers (not just webkit, but opera too) show these as errors is: we'll catch any invalid markup being added in other parts of the code. If we stop sending that content-type header, then we'll only notice invalid xml/xhtml sneaking in if we remember to use a validator - which i suspect we won't remember to do. _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
