Open Bug 219435 Opened 21 years ago Updated 12 years ago

Mouse clicks often ignored

Categories

(SeaMonkey :: UI Design, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: workshop, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.5b) Gecko/20030827
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.5b) Gecko/20030827

Mozilla often ignores single-clicks on links. Seems that the clicks I do are
slightly too short in duration for the browser because a slow click (hold the
L-mouse button down for a fraction of a second longer than normal) works.

Reproducible: Always

Steps to Reproduce:
1. Go to any web page and find a link. It helps if you are in a hurry.
2. Single left click on the link. If the test is successful, nothing should happen.
3. If step 2 was a success, then repeat but this time more slowly and the link
should work.


Actual Results:  
The (normal) quick left click is ignored.

Expected Results:  
Followed the link.

This does not happen in any other application on my machine. I'm running Windows
ME, 1.2Ghz CPU.
I just noticed that the browser even changes the colour of the link (in my case
to red) as though it were visited or active, but did not actually go to the link
URL.
I´ve seen this for some time, using Win98 on a Celeron 333 with 96 MB, often
swapping. The link gets surrounded with a little dotted line, but nothing happens.
I have exactly the same problem on Windows Me.
Flags: blocking1.6a?
Flags: blocking1.5-
Flags: blocking1.4.2+
Flags: blocking1.4.1+
Flags: blocking1.6a?
Flags: blocking1.5-
Flags: blocking1.4.2+
Flags: blocking1.4.1+
Same problem for me (Win98SE) with 1.4.1 and 1.5 (1.3.1 was Ok), seems to occur
when the mouse moving just a little (even if only 1 pixel !) during single-click
on the link => this is a selection operation so the link switch to red color.
And for me, same effect with tabs: if I move the mouse when single-click, tab is
only selected (grey color) but not activated !

With my soft mouse, I always move when I send single-click: Mozilla became
unusable !
still broken in 1.7RC1
still broken in 1.7RC2
still broken in 1.7rc3
Still broken in 1.7 release - getting tired of accidentally paying bills twice
or more because of the 3 or 4 clicks it takes to get a response.
Reproduced:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040608

This could be caused by both the OS (mouse drag threshold) or by another
behavior I've noticed during the last few releases.  Previously, a click would
register when a page was still loading - canceling the page load and loading the
clicked link.  Currently, the click is ignored unless the page is fully(?)
loaded.  This gives the impression of unresponsiveness.
It doesn't *seem* to be the OS as it only happens in Mozilla. While according to
the loading guage in the status bar, many pages *never* finish loading, it also
happens in fully loaded pages and in the Mozilla toolbar. I wonder if it may be
related to the one or two pixel shift in displayed graphics (most often .GIF
files) that I often see as the mouse passes over them.
Product: Browser → Seamonkey
*** This bug has been confirmed by popular vote. ***
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: general → guifeatures
Component: Browser-General → XP Apps: GUI Features
Product: Seamonkey → Core
QA Contact: general
Product: Core → Mozilla Application Suite
Filter "spam" on "guifeatures-nobody-20080610".
Assignee: guifeatures → nobody
QA Contact: guifeatures
Component: XP Apps: GUI Features → UI Design
this happens in firefox too. a LOT. and randomly. particularly with yahoo mail which seems to be a big web app. sometimes in yahoo mail when I click on a button, the hard disk will suddenly do a flurry of activity. but no action. I know that with XP, if the hard disk is going, the rest of the computer isn't (it has highest priority).
XP Pro Sp3 32-bit ff 14b9 I think, whatever the latest is right now).
in fact, it has happened in every version of firefox I have used.
somebody must be executing the mdb processor instruction (move and drop bits).
You need to log in before you can comment on or make changes to this bug.