-
Notifications
You must be signed in to change notification settings - Fork 0
What does browserSupportedMimes mean? #46
Copy link
Copy link
Open
Labels
AI assistedstatus: triageNeeds triage - check if valid and reproducibleNeeds triage - check if valid and reproducibletype: discussion💬 This issue is about gathering opinions and/or resolving dilemmas💬 This issue is about gathering opinions and/or resolving dilemmas
Description
Activity
Metadata
Metadata
Assignees
Labels
AI assistedstatus: triageNeeds triage - check if valid and reproducibleNeeds triage - check if valid and reproducibletype: discussion💬 This issue is about gathering opinions and/or resolving dilemmas💬 This issue is about gathering opinions and/or resolving dilemmas
browserSupportedMimesinlib/models/audios.tsandlib/models/videos.tsreads as a claim about what a browser can decode. It is not one, and some of what it lists no engine claims:canPlayTypeChromiumaudio/vorbisaudio/aacpvideo/mpegvideo/x-flvvideo/quicktimeNothing is broken by that. The list decides which files the viewer offers to open; the handler then either plays the bytes or reports an error, and a media element reads the bytes rather than the declared type. #45 measured that end of it: one WAV served as
audio/wav,audio/vnd.wave,audio/x-wavandapplication/octet-streamplayed in both engines, thoughcanPlayTypeanswers "no" foraudio/vnd.wave.So the question is what the list is meant to be, and the name should then say it:
handledMimesor similar is the honest name, and entries likeaudio/vorbisare harmless but pointless: vorbis is a codec insideaudio/ogg, not a container type a file carries.Worth deciding once for both handlers rather than per pull request.