gtk2 keyboard focus broken

RESOLVED EXPIRED

Status

()

--
major
RESOLVED EXPIRED
16 years ago
13 years ago

People

(Reporter: davh, Assigned: saari)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021020
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021020

cvs build from yesterday.
mozilla seems to think that it should use type ahead find 90% of the time.
Unfortunatly I cant reproduce, it simple happens when you've used the browser
long enough.
The only way to make mozilla behave again seems to be a restart.

Reproducible: Sometimes

Steps to Reproduce:
1. use browser until focus breaks
2.
3.

Actual Results:  
mozilla seems to think that all keyboard input is related to type ahead find.

Expected Results:  
behave it self ;)

Comment 1

16 years ago
Not a blocker.
Severity: blocker → major

Comment 2

15 years ago
I have seen this too, and I'm sad to see that it's almost a year old.  Anyway,
this might help out a bit:

The problems occurs a bit randomly like the reporter says.  BUT, I noticed that
there is in increased chance of it happening after opening a new tab that
contains a PDF using the Acrobat Reader plugin (w/Moz 1.3.1 and 1.4).

Comment 3

15 years ago
Oh, and I also found that there are a few 'primitive' actions that seem to set
the browser straight again:

- Click in the Address Bar a lot and press a bunch of keys randomly.  :)
- Open a new navigator window (in addition to the current one).  Simply opening
  the window won't fix it.  But, clicking and typing in the new window's Address
  Bar fixes the keyboard problem in the original window.  Then, I just close the
  new one.

Both of those 'workarounds' work pretty well, though.  I am using GTK2 with
Moz 1.4, btw.

Comment 4

14 years ago
I have a similar issue.

To reproduce:

Run any recent release of mozilla or firefox built with gtk2 in Linux.
Browse for a while, opening multiple windows.
Focus a browser window. Focus another.
At some point the browser that is focused, at least according to the window
manager, will not accept keyboard input, but the window that was previously
focused does receive it.
Closing the affected window and opening a new window suffices to clear it up.
The "other window" may be a mail client window as well.

The behavior doesn't happen with gtk1.

The bug manifests itself on two separate x86 machines. I'm using Enlightenment
as the window manager on both machines.

Comment 5

14 years ago
Also see bug #264815 
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.