[Webkit-unassigned] [Bug 202321] [GTK] Web Inspector: page error with shared-mime-info 1.14

[bugzilla-daemon at webkit.org]

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

--- Comment #22 from Bastien Nocera <bugzilla at hadess.net> ---
(In reply to Carlos Alberto Lopez Perez from comment #21)
> (In reply to Bastien Nocera from comment #20)
<snip>
> Well, the reality is that a file that ends in ".html" gets identified as XML
> since the mentioned commit in shared-mime-info. Not sure how a discussion
> about if shared-mime-info is a database, an API or a program helps here.

That means it can be used in different ways. The caller is the one that chooses whether to use content, or filename patterns, or a combination of both.

> 
> > Furthermore, shared-mime-info is built for end-users, not for programmers,
> > which aren't really supposed to know whether a webpage is HTML or XHTML.
> > shared-mime-info test suite needs to be fed some of the data that WebKitGTK
> > relies on to function properly.
> 
> That's news to me. How I'm supposed as end-user to use shared-mime-info? On
> my debian system the only program shared-mime-info includes is
> update-mime-database.

Its content is geared towards differentiating files for the benefit of end-users. If you need to know whether something is HTML, or XHTML, or which variant thereof, then you should implement it in your application/library. shared-mime-info does not aim to be a replacement for those, as you've seen.

Anyway, I don't think that carrying on the discussion here will have any effect. If there are identification bugs, please file MRs against shared-mime-info to extend the test suite to show those.

-- 
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/20191016/bd22dada/attachment.html>