When are you going to fix the horrendous bugs in FF 7.0.1?
On some websites, particularly eMusic and Amazon, FF 7.0.1 monopolizes both CPU and PF, so that the browser hangs or even crashes the machine. I understand several hundred other users have similar problems. Why is this version incompatible with Java? Isn't it time you fixed all this? If you can't, how do I reverse the 'update' and return to FF 6. I've had to revert to IE8 in the meanwhile.
Alle svar (8)
Because firefox 6 is unsupported and not secure it would not be recommended to do this. If you do need to downgrade it should be to firefox 3.6.23 (soon to be 3.6.24)
Firefox should not be crashing if it is see firefox crashes and follow the advice in that article and if necessary post back in this thread, or a new one.
What do you mean by "Why is this version incompatible with Java? " are you able to give full details please of an actual problem you are having ?
'Add-ons' clearly states 'Firefox 7.0.1 is incompatible with Java Console', and Java Console 6.0.3 to 6.0.7 are disabled.
What are you trying to use those for what is the specific problem ?
Most users probably are more interested in enabling javascript, than using troublesome java consoles.
- see also kb.mozillazine.org/Java#Java_Console "Can be safely removed by non-developers. "
I'm not. These were all automatic updates.
I'm still working on this, although it's very time-consuming. But, let's be clear: none, repeat none of these problems arose before the 'upgrade' to 7.0.1!
I did not try on Firefox 7, but on Firefox 9 Java does install, the java console may be used and the test at http://www.java.com/en/download/testjava.jsp completes ok.
Java is however normally unnecessary on my installation, and I keep it disabled most of the time. I suspect there may be some security concerns with unnecessary use of Java. (e.g. see texas.gov and MS )
Didn't know there was a FF9 -- is it a beta? Thanks for the points about Java; all good. Meanwhile, things seem to have improved enormously since I removed extensions Showcase and FastestFox(!).
I've just discovered I share one possible, if not probable cause of the problems with FF7.0.1 with lots of others: ping.chartbeat.net. Isn't it time Mozilla did something about this, and stopped pretending the problem doesn't exist?!