Closed Bug 267102 Opened 20 years ago Closed 19 years ago

Keyboard and mouse buffers are not synchronous.

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: itempower, Assigned: bugzilla)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10.1

When working on heavily loaded or old (and slow, like my P-Pro 233) systems 
problems arise with the keyboard and mouse buffers not being sync'd.

For instance, on a webpage, you can click a user editable text box and press 
CTRL-A. Then when the browser processes them from the buffer it will process 
them out of order (highlighting the entire page and then placing the mouse in 
the text box).

Another demonstration would be to open about 20 tabs of webpages then starting 
with the first, click on the fisrt tab then tap CTRL-A, repeat on the second 
tab, etc. until the last tab.  You would expect each tab to have it's page 
selected, but this is not the case.

This is not a problem if the user is willing to wait for the computer to 
process each event before sending another one, but this workaround (user 
patience) defeats the purpose of buffering keyboard and mouse events.

Reproducible: Always
Steps to Reproduce:
1. Use a realy slow computer
2. Bog the computer down
3. Start using mouse and keyboard shortcuts

Actual Results:  
The mouse and keyboard events were processed out of order.

Expected Results:  
The mouse and keyboard events should be sync'd in their buffers.

Throwing a mouse event token into the keyboard buffer when a mouse event is 
buffered and vice versa to allow for synchronous processing could fix this, 
also combining the two buffers into one would also fix this.
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
You need to log in before you can comment on or make changes to this bug.