Closed
Bug 24498
Opened 25 years ago
Closed 25 years ago
problems giving focus for keyboard scrolling
Categories
(Core :: XUL, defect, P3)
Tracking
()
People
(Reporter: dbaron, Assigned: trudelle)
Details
DESCRIPTION: When a page is loaded, the page should generally (although perhaps
not always) have the focus so that the up/down/PgUp/PgDown keys allow
keyboard-based scrolling. Right now this is not happening. Currently the
behavior that I am seeing is:
* when a page is loaded by clicking a link or bookmark:
+ initially, the arrow keys do nothing
+ if one clicks *in the page*, they give javascript errors as described in
bug 23656
+ if one clicks in the URL bar and then in the page, then they work.
This seems like some weird focus problem. Pages loaded by typing the URL in the
URL bar therefore work better (since they work once you click in the page,
although they should probably work without the click).
STEPS TO REPRODUCE:
1) load a web page
2) click on a link
3) try to scroll with the arrow keys
4) click in the page
5) repeat (3)
6) click in the URL bar
7) repeat (4)
8) repeat (3)
ACTUAL RESULTS:
* after (3), nothing happens
* after (5), javascript errors are given
* after (8), scrolling works
EXPECTED RESULTS:
* scrolling should work in all three cases
DOES NOT WORK CORRECTLY ON:
* Linux, mozilla, 2000-01-19-08-M13
WORKS CORRECTLY ON:
* NN 4.x, I believe
ADDITIONAL INFORMATION:
I believe the same descriptions apply to giving focus for tabbing through links,
although I haven't tested it too carefully.
I think there may be a number of other bugs that may attempt to describe this
one, but:
+ they may be assigned to the wrong person
+ they don't explain that the problem is related to focus and how to reproduce
the three different states
Assignee | ||
Comment 1•25 years ago
|
||
cc'ing saari, resolving as dup of Travis' bug: nsWebShell Key events not working
until focus set in window
*** This bug has been marked as a duplicate of 9701 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•