Properly made plugins shouldn't have been affected by Firefox updates. However, most extensions on the other hand have needed "tweaking" for each new version that was released last year; although extensions that were hosted at the official Mozilla Add-ons website have had the benefit of being automatically updated for each new version as long as the extension passed the "coding scan" for compatibility. IOW, most extension developers using AMO didn't have that problem.

That is going to be different as of Firefox 10, which is slated for release on Jan 31. Extensions will be assumed to be compatible and won't automatically be disabled just because of the update.

According to this page - http://twonky.com/support/downloads.aspx - Twonky is dropping TwonkyBeam support for Windows PC's with any browser. So it looks like them blaming it on Mozilla is kind of disingenuous.

"Please note that TwonkyBeam 1.9 for Internet Explorer will be our last release of this product. While it will not expire, we are no longer going to provide updates. We are also no longer able to support TwonkyBeam for any other browsers"

I'm seeing a disturbing trend with Firefox. Each "upgrade" is slower to load and buggy. I lost my address bar function with the 10.0 upgrade, and had to waste time finding out that it was incompatible with AVG SafeSearch. And your six week upgrade cycle is ridiculous. How about taking a bit more time and just doing it right? I've been a faithful FF user for quite a while, but at this rate, you're going to lose me.

Even more pathetic, your “Submit Feedback” button doesn’t work.

Blaming Mozilla for problems caused by add-on is kind of disingenuous.

Each new version of Firefox goes thru an 18 week build cycle, going thru 3 separate "channels" of development. The last 6 week Beta channel is when companies like AVG should (at a minimum) be testing their Firefox add-ons for compatibility issues, so they have the time to fix their crap before a new version of Firefox is released.

What's really disturbing is that you fail to realize that as far as Firefox add-ons are concerned, Firefox is the main application and that anyone who creates an add-on for Firefox is responsible for testing their stuff, and fixing it when/if it breaks, or when it breaks Firefox.

In conclusion, the AVG Safe Browsing add-on doesn't really add anything of value to Firefox, it merely replaces a built-in feature, and adds a few "bells & whistles" to Firefox.

these opinions are expressed by a support contributor who doesn't work for Mozilla

Right on! Thanks for your comment. Lets slow down the development cycle.

http://input.mozilla.org/en-US/feedback#sad For several versions now (I think since 10) the password request doesn't come up until I'm done with, in this case, banking. In other words, Firefox let me sign in to the banking site and complete my transactions never once asking for the password. It wasn't until I quit Firefox that the boxed-in request for the password came up. I shudder to think what would happen if somebody (not necessarily bad or evil, but of course that) sat down in front of my computer and proceeded to launch Firefox, never once getting a password request until quitting. I imagine they would just walk away, (evil) deed accomplished. Is there another way to lock Firefox?

Firefox 12.0 in OS X 10.6.8 on MacBook Pro (model 5,1)

Submit Feedback in Firefox doesn't work! The only things blocked by Ghostery were WebTrends and New Relic, but when I unblocked them Submit still didn't work. Using Camino now to post this.