Plugin pages eat key strokes that location bar should get




13 years ago
5 years ago


(Reporter: William Bardwell, Unassigned)



Firefox Tracking Flags

(Not tracked)





13 years ago
If you load a full page plugin handle file type,
and go to the location bar, and type in it, when you
move the mouse down over the plugin page (even with
click to focus), the location bar stops getting key
presses.  It will get key presses again if you move the
mouse pointer over any part of the browser provided UI.

If you load an HTML page, and click in the location bar,
the key strokes continue to go to the location bar when
you move the mouse over the web page, until you click on
the web page.  This is what I would expect the plugin case
to do.
I'm betting the problem is that X is delivering the key events to the plugin
widget and the plugin is simply never passing them on to us.... so we have no
idea a key was even pressed.
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:

Comment 3

12 years ago
Still a problem.  I am not convinced by that explaination, since all
plugins seem to show the same behavior.  Maybe the browser created window
that is passed to the plugins is the problem window?

Comment 4

12 years ago
marking NEW although it might not be fixable
Ever confirmed: true


5 years ago
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.