Closed Bug 195152 Opened 22 years ago Closed 19 years ago

Dragging image over right-click menu freezes X server

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: fry, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210

Dragging image while right-click menu is activated (hard to do but possible)
will lock up X until mozilla-bin is killed.

Reproducible: Sometimes

Steps to Reproduce:
1. Go to an arbitrary Web site, e.g. www.mozilla.org
2. Place mouse cursor over an image, e.g. the logo in top left corner.
2. Click and hold left mouse button, then click and hold right mouse button
3. Release left mouse button while keeping right mouse button held down
4. If/when right-click menu appears, move mouse cursor to right. May have to
move it left again and/or wave it around for a second or two.

Actual Results:  
Mozilla freezes about 80% of the time, along with all other X applications (at
least under KDE 2.2.2, XFree86 4.2.0). X functions normally after I telnet in
from another machine and kill mozilla-bin.


Expected Results:  
Anything but freeze.

KDE 2.2.2, XFree86 4.2.0, Slackware Linux 8.0 (much patched), tdfx server with
16MB Voodoo3 PCI
I'm seeing problems with linux trunk 20030226 as well, but the freeze is not
permanent.  If i wait a bit, things go back to normal.

Mozilla doesn't handle both buttons being pushed well. there's a bug on that
somewhere...
Does hitting the Esc button help?
Yes, the ESC key does unfreeze everything!
Assignee: asa → events
Component: Browser-General → Event Handling
QA Contact: asa → ian
this worksforme with linux trunk (gtk1 and gtk2), but might have been fixed in
the X server.

fry: are you still seeing this bug?
Couldn't replicate it on current setup (Mozilla 1.7.5 / KDE 3.0.1 / XFree86
4.2.0) . Will check on other machines too. Thanks everyone.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.