Strange mouse behavior when holding down both buttons and moving over context menu

NEW
Unassigned

Status

()

Core
Event Handling
--
minor
15 years ago
8 years ago

People

(Reporter: Jens Kager, Unassigned)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827

After clicking and holding both mouse buttons inside a marked text portion,
mouse clicks seem to go unnoticed to the whole system when the cursor is moved
inside the appearing context menu and out of it again - until you press Escape.
Meanwhile you see that "add cursor" which appears when, e. g., adding a mail
item to another folder in MailNews by dragging and holding the Control key.

While the usage described above may not be normal usage, I find it happening to
me quite often when I play around with my mouse while reading something, lost in
thought. And it sure is annoying.

Reproducible: Always

Steps to Reproduce:
1. Mark any text.
2. Click and hold down both mouse buttons simultaneously somewhere inside the
marked text.
3. Still holding down the buttons, move the cursor over the context menu, and
out of it again.
Actual Results:  
You can't click anymore with the mouse, anywhere on the desktop. You've got to
press Escape to make the cursor return to normal.

Expected Results:  
Nothing special.
Confirming and over to events.. we seem to enter a drag session for some reason...
Assignee: asa → joki
Status: UNCONFIRMED → NEW
Component: Browser-General → Event Handling
Ever confirmed: true
QA Contact: asa → rakeshmishra

Updated

15 years ago
QA Contact: rakeshmishra → trix
(Reporter)

Comment 2

15 years ago
Any news on this bug? I'm still seeing this problem with 1.3a (Build ID 2002121222).

Comment 3

15 years ago
.
Assignee: joki → saari
QA Contact: trix → ian
Assignee: saari → nobody
QA Contact: ian → events
(Reporter)

Comment 4

8 years ago
I think this ancient bug can be closed. Can't reproduce the behavior with Firefox 3.0.13 - I don't know whether FF 3 even contains any of the code which was responsible for the bug seven years ago.
You need to log in before you can comment on or make changes to this bug.