Description of problem: When specifying an mp4 as url, firefox shows a funny screen which claims that the file is corrupt (which it isn't) and doesn't offer an option to save the file. Version-Release number of selected component (if applicable): firefox-38.1.0-1.mga5 How reproducible: Always Steps to Reproduce: 1. point firefox to http://distribution.bbb3d.renderfarming.net/video/mp4/bbb_sunflower_2160p_30fps_stereo_abl.mp4 2. watch the result: http://vserver.13thfloor.at/Stuff/MAGEIA/BUGS/firefox_mp4.png 3. Reproducible: Steps to Reproduce:
I can confirm with the bbb_sunflower video linked above, but other mp4 videos work just fine: http://techslides.com/demos/sample-videos/small.mp4 Most likely the bbb_sunflower one is using a codec that our Firefox does not support out of the box.
Summary: Firefox claims that mp4s are corrupt and denies option to save them. => Firefox claims that some mp4 videos are corrupt when they can be played locally
Okay, so how do I get firefox not to handle the file and allow me to download it for example?
CC: (none) => herbert
I don't know, I'm just providing more info in this bug report.
(In reply to Herbert Poetzl from comment #2) > Okay, so how do I get firefox not to handle the file and allow me to > download it for example? You could use Ctrl + S - it should offer you to save the file.
CC: (none) => mageia
Indeed it does, but I think the problem is more a general, that firefox doesn't consider the user capable of deciding what to do with files based on extension or mime type. For example, I would prefer and always decide to save this type of file, but the firefox developers have their own idea what the correct action is, regardless of the user's preference. In any case, thanks for the "workaround".
(In reply to Herbert Poetzl from comment #5) > Indeed it does, but I think the problem is more a general, that firefox > doesn't consider the user capable of deciding what to do with files based on > extension or mime type. > > For example, I would prefer and always decide to save this type of file, but > the firefox developers have their own idea what the correct action is, > regardless of the user's preference. > Well, there's nothing we can do about such upstream decisions, at least not with the "vast" amount of packagers we have (or do you volunteer to patch FF and to maintain the patch?) Closing as wontfix
Status: NEW => RESOLVEDCC: (none) => marja11Resolution: (none) => WONTFIX