User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:126.96.36.199) Gecko/2009042523 Ubuntu/9.04 (jaunty) Firefox/3.0.10 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:188.8.131.52) Gecko/2009042523 Ubuntu/9.04 (jaunty) Firefox/3.0.10 When FF is running java applets (in a https secure system) quiting via the normal qai: logout, click on quit symbol (X) or via the file menu does not stop ff from running: the proces is still alive but the FF window is not visible. At restarting FF a warning screen tells that FF is still running and should be stopped first. The System Momitor shows max. load on one of the Phenom cores and high loads on the others. Typing in input fields reverses direrection (typeing backwards ...) N.B. this is a reproducable error! I can stop FF via the System Monitor Reproducible: Always Steps to Reproduce: 1.Go to url: https;www/binck.nl (you need an account, but this is the only site where I experience this problem) 2.check one of the tabs and go back to the home tab: the monitor bar tells you a applet is started 3.quid FF (and observe the System Monitor) Expected Results: FF process stops after quiting
correction: When java script is disabled in the content preference this problem doesn't exist. But then needed functionality is not available. In my opinion: closing a FF url (deleting a FF tab) should stop all related [java] processes.
Observation: input fields are working backwards!!!! Even in other open tabs. Example: typing "Firefox" results in "xoferiF" This is weird the first time you experience it ...
This is a mass search for bugs which are in the Firefox General component, are UNCO, have not been changed for 500 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.