bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.

[qt]really slow browser results in double-key entry



14 years ago
13 years ago


(Reporter: lkcl, Unassigned)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040928 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040928 Firefox/0.9.3

this report is, i believe, related to the key focus weirdo problem where key
focus ends up on the previous tab or window (you know, the one that's been
around for ages).

i've been compiling the mozilla-qt port and running it over a wireless remote X
session (_not_ using NoMachine) so it's pretty horribly slow.

when entering text in a URL, i notice that there are double-key presses: keys
pressed once result in two letters appearing; sometimes a key pressed is not
seen at all.

i believe that there may be some underlying race condition that is screwing up
keyboard events, which sometimes results in key events - not on some window
managers as was suspected but on some slower or busier computers - going astray.

i hadn't realised that mozilla even has its own event management system
(allowing it to easily be ported to other windowing systems) otherwise i would
have mentioned this possibility earlier.

Reproducible: Sometimes
Steps to Reproduce:
1. make computer really slow:

  (cat /dev/zero > /dev/null; !!; !!; !!; !!; !!; !!; !!; !!; !!;
   cat /dev/urandom > /dev/null; !!; !!; !! 
   and other tricks)

2. start using mozilla, typing in url input box for example.
Summary: really slow browser results in double-key entry → [qt]really slow browser results in double-key entry

Comment 1

14 years ago
regarding the change to this bug, which classifies it as a "qt-only" bug:

my feeling is that there is an underlying and long-standing bug in mozilla's
event handler, of which this _particular_ "bug" is just one of a long-standing
set of symptoms.

e.g. sometimes keyboard focus is lost, having clicked on a new link, such that
up and down arrow do not work in moving the scrollbar of a page up and down
until you click somewhere on the page (not on a link).

e.g. my favourite one where you open a new window and _sometimes_ the keyboard
focus remains on the window behind (!) i've documented this one before and it is
"believed" by the mozilla community to be related to specific window managers
only (e.g. fvwm2)

whereas i believe it to be a race condition somwehere in the event handler.

and therefore nothing _specifically_ to do with the QT port.
Product: Browser → Seamonkey
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.