on 03.01.2008 23:06, Max Barel at [EMAIL PROTECTED] wrote: > As I know no way to guess xhtml capability from javascript and modify > this default header, webkit gets xhtml served as text/html. > > Does this qualify for a bug report or a feature request or do I miss > something?
We could probably change the default to match Firefox, but I do not really see the logic behind using the same Accept string for main resource loading and for XHR, given that Firefox itself uses different Accept strings for subresources. As you said, serving as XHTML is your policy. Obviously, the priority of the bug would be higher if it cited technical reasons for this policy, as it would mean that many people could benefit from a fix. > Side note: > As long as the correct namespace is used, document content is almost > OK. Almost because every linefeed between elements created from ajax > data is displayed as #cdata-section in the web inspector. Is this a difference from Firefox? This sounds like something worth investigating to me. - WBR, Alexey Proskuryakov. _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo/webkit-dev
