Focus for keyboard paging not set to active frame




13 years ago
7 years ago


(Reporter: Thomas Wolff, Unassigned)


Firefox Tracking Flags

(Not tracked)




13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10

When a frame is loaded with new contents in a frameset (e.g. clicked 
from a navigation frame in that frameset), the focus should be set 
to it for paging; but Page Up/Down and Space keys do not work for 
paging until the mouse is clicked into the frame.

Maybe this is a feature request rather than a bug report but I think 
it is so obvious that this is the desired behaviour that I consider it 
a major user interface issue. Of course there are ambiguous cases when 
multiple frames are loaded but when and where I can scroll a frame with 
the mouse wheel I certainly expect keyboard paging to work as well.

Reproducible: Always
Steps to Reproduce:
1. Load a frameset with navigation frame (e.g.
2. Move mouse over main frame, scroll wheel: works, press PageDown: nothing
3. Click other frame from navigation area
4. Move mouse over main frame, scroll wheel: works, press PageDown: nothing
Actual Results:  
keyboard control does not work

Expected Results:  
should work

searched bugs database for "focus", "focus active", "focus click", 
"no focus", "not focussed" - sorry if there is a duplicate that I didn't 
see in the long result lists
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041006

click in the frame followed by arrow down 


Comment 2

13 years ago
> click in the frame followed by arrow down
That's just what I complained about - that you have to click 
before the keys work. I think that's not intuitive after you've 
just loaded something into the frame and the usability should 
be improved here.
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 4

12 years ago
I'm refreshing the request for improving the user experience as described.
Assignee: bross2 → nobody
Confirming as a valid RFE. I don't think this is UI we want though.
Severity: normal → enhancement
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.