Conversation
|
@padenot Note that supporting the Browsers having implemented FLAC support does not inherently indicate support for sniffing it, and the linked bugs are for such general FLAC support, not explicitly for sniffing. While I do see that sniffing was added alongside the Firefox implementation (1ce419e3955f, e42414eeeabe), I am not seeing that in the Chrome/Chromium implementation. Are you able to point more directly to where Chrome/Chromium is doing the sniffing? Separately, your own recent Firefox bugs/commits on this topic may also be of relevance: |
|
I think I found where Chromium is sniffing for FLAC, which seems to predate its adding support for FLAC and also uses the MIME type It doesn't appear to have changed since 2013: I don't know the ramifications of this. @annevk Does seem like enough information to merge this? |
|
If you navigate to a FLAC file directly (or in an iframe) and it doesn't have |
|
In a browsing context, Chrome identifies this as |
|
And Chrome also tries to render it as text and not offer playback? |
|
Yeah, Chrome just displays the |
(See WHATWG Working Mode: Changes for more details.)
Preview | Diff