[Webkit-unassigned] [Bug 278992] Entity 'commat' not defined
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Sep 10 16:33:02 PDT 2024
https://bugs.webkit.org/show_bug.cgi?id=278992
--- Comment #9 from Michael Catanzaro <mcatanzaro at redhat.com> ---
> The xmlns attribute has no effect on guessing the document type (HTML or XML):
Huh, I didn't know that. Good find. Then shared-mime-info should probably stop matching on this to detect XHTML.
> If the resource is retrieved directly from the file system, set supplied-type to the MIME type provided by the file system.
I'm not sure what this means, because filesystems obviously do not have any concept of MIME type. That's not how computers work? We take the MIME type guessed by shared-mime-info, which I guess is the closest possible approximation.
> - Finally, the association between filename extensions and MIME types exists in UNIX-type systems at `etc/mime.types` and can be seen as a way for the filesystem to provide the MIME type (https://en.wikipedia.org/wiki/Media_type#mime.types).
Huh, I've never heard of /etc/mime.types. I doubt shared-mime-info looks at it. On my computer, that file is owned by mailcap, which I've never heard of. :) But I guess what this really indicates is that the spec authors' definition of "filesystem" is pretty flexible and can means whatever the browser wants it to mean. Anyway, for us, that's shared-mime-info.
I think shared-mime-info decides for itself whether content sniffing magic or file extension has higher priority? But I'm not sure. It's just one big data file, so you could probably experiment easily enough without needing to be a software developer. Seems we need the file extension ought to take precedence over content sniffing magic.
Guess: it maybe broke in: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/4961dc3e48d13c0c675ad7c135419b864813ca55
Or possibly: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/8ae13a589577e9bda12fb16465a03cd81b1cd349 which actually references our bug #160347, which it seems got forgotten long ago....
--
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/20240910/ebda755d/attachment-0001.htm>
More information about the webkit-unassigned
mailing list