Not a pure 'issue' per se, but I couldn't find a better place to get the point across.
This is the third, in a row, major release level of Mozilla that has broken existin… (read more)
Not a pure 'issue' per se, but I couldn't find a better place to get the point across.
This is the third, in a row, major release level of Mozilla that has broken existing plug-ins. While I do realize that there is 'some' need to update the plug-in engine to allow for better usability, better security and (theoretically) better memory/system resource management, this is absurd. Honestly, this is the last massive update to Firefox I'm going to use, at all, if this goes into V7. There is likely no perceptible change to the user base, other than deep and abiding aggravation and annoyance. Indeed, since R4, I've had problems with Google's Toolbar. A product they have since opted to drop further development for, in no small part because of these repeated changes. Can you list for me the specific code changes that were absolutely *necessary* for these later updates that caused the toolbar to become too much work for Google's support?
I realize this is a free product, and you don't actually need just one user's support. I can say, however, that I have tried to fend off gripes and complaints and other friends of mine having 'sworn off' FF for years now. If this continues, I will happily swap over to Chrome support instead, and not look back.
