Closed Bug 317995 Opened 19 years ago Closed 19 years ago

Closing a window with Java Plugin via All-In-One Gestures (0.17.4) causes unresponsiveness

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: schiefer, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 After closing a window with a java plugin -- an applet from the teamtrack ticket system in this case -- firefox won't response anymore. When closing the last window, a firefox process - and the java plugin icon - will remain and one can't open another window since "firefox is already running". Reproducible: Always Steps to Reproduce: 1. Go on a site with java applets, preferably from teamtrack 2. close the window 3. Actual Results: firefox will become unresponsive Expected Results: not becoming unresponsive? ;-)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051127 Firefox/1.6a1 ID:2005112705 WFM. Can you provide a link to such a page (don't know teamtrack)? Does it also happen in the safemode or with a new profile? http://kb.mozillazine.org/Safe_mode http://kb.mozillazine.org/Profile_Folder
You are right: It seems to be a problem with the All-In-One Gestures extension (0.17.4). When I close the window via via menu or close window button everything is fine, but when I use the mouse gesture from the extension firefox hangs.
Component: General → Extension/Theme Manager
Summary: Closing a window with Java Plugin causes unresponsiveness → Closing a window with Java Plugin via All-In-One Gestures (0.17.4) causes unresponsiveness
Problems with extensions should be taken up with the extension owner.
Component: Extension/Theme Manager → General
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
*** Bug 318551 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.