搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

why does firefox drop support for a plugin with an update

  • 2 回覆
  • 3 有這個問題
  • 1 次檢視
  • 最近回覆由 Krammig

more options

Why the H*ll does Firefox drop support for a plugin when there is an update in Firefox.

FF4 has reported that 6 of my plugins that work fine in 3.6 are now not supported. !! This is a joke, and happens regularly.

As a user (a highly IT literate one) this is annoying and frustrating, and from a design standpoint, unprofessional.

Why the H*ll does Firefox drop support for a plugin when there is an update in Firefox. FF4 has reported that 6 of my plugins that work fine in 3.6 are now not supported. !! This is a joke, and happens regularly. As a user (a highly IT literate one) this is annoying and frustrating, and from a design standpoint, unprofessional.

所有回覆 (2)

more options

Plugins as in Flash, Java, quicktime or such or do you mean Extensions ?

Plenty of Plugins seems to be detected and in use by Firefox 4.0 just fine according to your system details by your post.

If you meant Extensions then check for updates, look at addons.mozilla.org or the Extension homepage for to see if the author has provided a update.

Generally Extensions can need anywhere from a simple maxversion bump to a lot more for it to work properly on a new Major version of Firefox depending on what the Extension does.

It is professional actually as extensions that were not actually compatible may actually cause problems big or small if they were to still just work in a new Major version release so hence the need for them to be properly up to date on any changes and hopefully the extension author is quick about it.

由 James 於 修改

more options

Thank you for the swift reply, and I appreciate the comments.

Your last paragraph pretty much sums up my concerns. If an extension or plugin works in 3.4 it should work in 3.6 and above. More over if it works in 3.6 it should work in 4

The core product (Firefox) should not be so drastically changed with a new release that it causes items that used to work, to now not work. This is a headache for Developers and Users.

I do appreciate that in some instances it is a matter of the Developer to simply update the internal "compatibility version" but I would think this is done for the most part.