Closed
Bug 15629
Opened 26 years ago
Closed 26 years ago
Page Up/Down/Home/End/etc require explicit focus placement
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Core
DOM: UI Events & Focus Handling
Tracking
()
People
(Reporter: elig, Assigned: joki)
Details
(This must be a duplicate, but I can't find any branched off of 12673, and am
thus writing up.)
* TITLE/SUMMARY
Page Up/Down/Home/End/etc require explicit placement of focus
* STEPS TO REPRODUCE
0) Launch Apprunner
1) View any web page (I viewed http://sauron.unh.edu/images/fantasy/jjusko/
jj_15.jpg, from bug #10018)
2) Press the page down, home, end, page up, arrow keys, etc.
* RESULT
- What happened
Nothing. You must specifically place the focus within the browser window before
any of the navigation keys do anything.
- What was expected
Focus to be automatically placed for keyboard commands, as is the case in other
popular browsers (well, IE. ;)
* REGRESSION
- Occurs On
Mac OS Apprunner (1999100120 optimized build)
Win32 Apprunner (1999100319 optimized build [NT 4, Service Pack 5])
Linux Apprunner (1999100118 optimized build [NT 4, Service Pack 5])
- Doesn't Occur On
Communicator 4.7 RTM (Mac OS)
Internet Explorer 5 RTM (Win32)
* CONFIGURATIONS TESTED
- [Mac] Beige Power Mac G3 (266 MHz PowerPC 750), 96 MB RAM (VM on; 1 MB of VM
used), 1024x768 (Thousands of Colors), Mac OS 8.6
- [Win32] Vectra VL (233 MHz P2), 96 MB RAM, 800x600 (True Color), NT 4.0 SP5.
- [Linux] Vectra VL (266 MHz P2), 96 MB RAM. Red Hat Linux 6.0 (GNOME).
Reporter | ||
Updated•26 years ago
|
QA Contact: janc → elig
Reporter | ||
Comment 1•26 years ago
|
||
[QA Assigning to self.]
Assignee | ||
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 3•26 years ago
|
||
Wow. Now *that's* a bug with a lot of duplicates. ;)
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•