Closed Bug 34796 Opened 25 years ago Closed 25 years ago

setting focus after search box entry

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED DUPLICATE of bug 9701

People

(Reporter: jfdecd, Assigned: asa)

References

()

Details

When clicking in the search box area, putting in a URL or doing a search, the focus should then be placed into the page area so that the user can press down arrow to scroll or pagedown or pageup. To reproduce: 1. Click in Search box area. Enter in a URL. 2. Press Enter key. 3. (Now) you must click in the page area and then the downarrow, pageup and pagedown keys will do what they are supposed to. What needs to happen is that after step 2 the user should NOT have to click into the page area to do the pageup, pagedown, and up/down arrow keys to start scrolling.
This could be a dupe of bug 9701, "nsWebShell Key events not working until focus set in window (TAB, PgDn, ALT+, CTRL+)", but we can't tell because we don't know what build the reporter was using. jfdecd@execpc.com - what is the Build ID of your build (bottom right corner of browser window)? Gerv
Resolving as a dupe of bug 9701, given lack of input from reporter. Gerv *** This bug has been marked as a duplicate of 9701 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
This still exists on linux using build 2000050820. To repeat: load www.excite.com make sure there is a scrollbar on the right. click into the search text box. hit up,down,page up, or page down buttons on the keyboard. notice that none respond. Expected result: page moves with key presses. (as in N4.72) Actual result: key presses (up,down,page up,page down) are ignored. after further research, I've found that this is a duplicate of bug 27771. I'm marking verified, rather than reopening and reduping.
Status: RESOLVED → VERIFIED
Component: Browser-General → Event Handling
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.