Closed Bug 293369 Opened 20 years ago Closed 19 years ago

Arrow keys, when held down, will not continue to scroll over flash ads and forms.

Categories

(Firefox :: General, defect)

1.0 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 95541

People

(Reporter: aciel, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050502 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050502 Firefox/1.0.3

Theoretically, if you hold down the arrow key and it starts scrolling, it
shouldn't stop until either you release the key or you reach the end of the
page. In Firefox, however, as soon as the mouse cursor is positioned over a
Flash thing, the page stops scrolling and the cursor must be moved to continue.

This is really, really annoying.

Reproducible: Always

Steps to Reproduce:
1. Go to the given URL, and place the mouse cursor somewhere near the top of the
left-hand column.
2. Hold down the down arrow key.

Actual Results:  
Scrolling stops about half way down, when the mouse cursor is over a Flash object.

Expected Results:  
Seems like Flash should only override the normal keyboard controls if it has
behaviors defined for those keys, or SOMETHING.

Certainly, if the arrow key is held down, it shouldn't be co-opted by a Flash
applet.

Gentoo Linux, KDE, with GTK installed. The Flash player was installed through
Firefox, not externally; though in the past I've installed it manually and it
has exhibited the same behavior.
WFM in Windows. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2)
Gecko/20050507 Firefox/1.0+
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/
It still does it in 1.0.6.
Version: unspecified → 1.0 Branch
And in Firefox 1.5 beta 2 (which is what the auto-reolve mail wanted to know) ?
I've just tested this with a current CVS checkout of Mozilla Firefox 1.6a1, and
it shows the same (annoying) behaviour.
This might be a window manager issue? Maybe you have hover focus turned on in
your windowing manager.

Marking confirmed due to multiple people seeing same bug.
Status: UNCONFIRMED → NEW
Ever confirmed: true
In that case I will add that I am using KDE 3.4.x. Anyone using anything
different getting this error?
I noticed the flash <object> tag on the URL provided contains no wmode param, so
it's using wmode="window" by default. AFAIK, both QT and GTK have options for
"Focus window on mouseover" (or something like that). You can check by looking
in the KDE Control Panel or whatever. Try disabling anything for raising or
focusing windows on mouse event. If this fixes it, FF should probably be
blocking out these events, but isn't.
Yeah, I don't have those options for changing window focus on mouse over set, so
it seems to be a FF issue.
I see this behaviour using IceWM without any hover focus set. IceWM uses neither
QT nor GTK, if I am not mistaken.
It seems to me that there's an earlier report about this bug - number 95541, filed 8.15.2001. Sorry if I'm wrong, but this seems like a duplicate.

*** This bug has been marked as a duplicate of 95541 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Sorry about my duplicate duplicate report :-/ I did though search this page for any mentions about duplicacy with 95541 before sending my comment! I didn't come to think that the search function doesn't search the whole page, but just the end of it (unless you tell it otherwise) and propably for that reason missed the remark about 95541 at the beginning of the page. Perhaps there should be three buttons on the search bar: Search backwords, Search forward and Search the whole page (with different words perhaps :-) But I guess I'll better stop misusing this bugreport now...
You need to log in before you can comment on or make changes to this bug.