[Webkit-unassigned] [Bug 201545] [GTK] Consider dropping content type sniffing

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=201545

--- Comment #12 from Alexey Proskuryakov <ap at webkit.org> ---
>  * The document http://www.linuxfromscratch.org/blfs/view/systemd/index.html is broken for attempting to declare a custom encoding in an XHTML document. The XHTML document is invalid.

I didn't check if this particular document is valid XHML other than having an incorrect character encoding. It's not very important for two reasons:

1. One error is enough to break everything in XML.

2. There are lots of HTML documents on the web that have pieces of XML in them, but are very broken in many ways were they to ever be parsed as XML. It's OK, and HTML5 defines error handling that prevents any functional differences between browsers.

>  * The website http://www.linuxfromscratch.org is further broken since it uses HTML content type for an XHTML document with HTML content type. (It so happens that using the wrong content type is required to avoid the first problem.)

We should never ask websites to move from HTML to XHTML. That would regress behavior for customers (no incremental rendering, very high chance of catastrophic failure like of this sort).

So server behavior is correct and desirable.

>  * Finally, WebKitGTK is (arguably) ill-advised in sniffing the document contents to determine content type. It seems Safari and other browsers consider only the file extension, .html. WebKitGTK should aim to match the behavior of other browsers.

Yes.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190911/2126987c/attachment.html>