We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefox 45 not honoring quicktime plugin Applications setting

  • 3 个回答
  • 1 人有此问题
  • 3 次查看
  • 最后回复者为 cor-el

more options

Our internal site has a page that displays a video via an embedded object the Quicktime plugin. The video source in the page might be "/sample.mov", and is standard H.264, delivered with Content-type of "video/quicktime". Firefox has had its Applications settings set to handle this with the Quicktime plugin. The page works fine both with Firefox 45 and previously - the Quicktime plugin plays the movie.

If you retrieved the "/sample.mov" URL directly in Firefix <45, it also worked as expected, with Firefox using Quicktime to play the video. However, with Firefox 45, Firefox uses its own video player for the URL-based request, not Quicktime. Presumably for some reason the Application setting for "video/quicktime" is now being ignored. I'm not sure if this was a deliberate change or some sort of unintended side effect. I just wanted to see if anyone could shed any light on this before digging in further? FWIW, this is Firefox 45.0.1 (32 bit) on Windows 7, with various versions of Quicktime from 7.7.4-7.7.9. I know Firefox 43 did the "right" thing and used the Applications setting in the direct URL case.

I know plug-in support is on the way out, but until then this is unfortunate, since the Quicktime plugin supports single-frame advance and is preferred here for our purpose while still possible.

Our internal site has a page that displays a video via an embedded object the Quicktime plugin. The video source in the page might be "/sample.mov", and is standard H.264, delivered with Content-type of "video/quicktime". Firefox has had its Applications settings set to handle this with the Quicktime plugin. The page works fine both with Firefox 45 and previously - the Quicktime plugin plays the movie. If you retrieved the "/sample.mov" URL directly in Firefix <45, it also worked as expected, with Firefox using Quicktime to play the video. However, with Firefox 45, Firefox uses its own video player for the URL-based request, not Quicktime. Presumably for some reason the Application setting for "video/quicktime" is now being ignored. I'm not sure if this was a deliberate change or some sort of unintended side effect. I just wanted to see if anyone could shed any light on this before digging in further? FWIW, this is Firefox 45.0.1 (32 bit) on Windows 7, with various versions of Quicktime from 7.7.4-7.7.9. I know Firefox 43 did the "right" thing and used the Applications setting in the direct URL case. I know plug-in support is on the way out, but until then this is unfortunate, since the Quicktime plugin supports single-frame advance and is preferred here for our purpose while still possible.

所有回复 (3)

more options

You can try to set media.apple.mp4.enabled to false on the about:config page.

You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.

You can also check other media*.mp4.enabled prefs as I don't know which are present on Mac.

more options

For clarity, there are no Macs involved in the problem (although I am posting this from a Mac). There's no "media.apple.mp4.enabled" pref on the Windows 7/FF45.0.1/QT 7.7.9 setup I'm testing with. There are "media.mp4.enabled" and "media.mediasource.mp4.enabled" ones, both true.

I'll have to do some digging in to Bugzilla and elsewhere to see exactly what these are controlling, but at first blush I'm not looking to globally disable any playback technology, but have Firefox honor its Applications settings and play a "naked" video/quicktime response with the Quicktime plugin, as it did prior to FF45.

more options

Try to set media.play-stand-alone to false.