445654 - Keyboard Scrolling Disabled After Booting

Status: RESOLVED WORKSFORME

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

Description

[David E. Ross]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.16) Gecko/20080702 SeaMonkey/1.1.11

When I start SeaMonkey after a reboot (and sometimes without even the reboot), keyboard scrolling does not work.  This includes the arrow, Home, End, Page Up, and Page Down keys.  I can use my mouse to scroll but not the keyboard.  

Other applications accept keyboard inputs, so I know my keyboard is connected and working.  

The browser window has focus.  I can click within the rendered window several times, but keyboard scrolling remains disabled.  In any case, if the window did not have focus, I don't think mouse scrolling would work.  

Reproducible: Sometimes

Steps to Reproduce:
1.  Launch SeaMonkey.  
2.  When home page loads, press down-arrow key to scroll.  
Actual Results:  
Page does not scroll.  

Expected Results:  
Page should scroll.  

Launching certain browser managers enables keyboard scrolling.  These include Bookmark Manager and Preferences but not Profile Manager.  

Selecting a link to another page enables keyboard scrolling.

Comment 1

[Tony Mechelynck [:tonymec]]

IIUC, keyboard scrolling requires not only that the browser window have focus, but that its _content_ have focus. If some chrome button, menu, or location/search bar has focus, <Down> won't scroll the page content.

Can you verify that if you hit <Tab> enough times to move the focus out of the chrome and into the page content, or if you click anywhere in the page content (but, in both cases, not in a textarea), the page becomes scrollable?

Comment 2

[David E. Ross]

My home page that I see when I launch SeaMonkey is my bookmarks file.  

I can repeatedly click on the page away from any link.  That does not resolve the problem.  Clicking on a link does resolve the problem.  

The next time it happens, I'll try the Tab key.  

The problem has not yet happened today.  

Comment 3

[David E. Ross]

The problem just now happened, when I launched SeaMonkey right after a cold bootup of Windows.  

Per comment #1, I tried using the tab key.  I saw links in my home page (my bookmarks file) sequentially selected.  However, that did not resolve the problem.  

I right-clicked my mouse to get the pull-down context menu and selected View Page Info.  That did not resolve the problem.   When I I right-clicked my mouse to get the pull-down context menu and selected View Page Source, however, the problem went away.  

Note that, after using my mouse to drag the vertical scroll bar or selecting the scroll triangles in the scroll area, the problem is NOT resolved.   

Comment 4

[David E. Ross]

Today, I discovered another work-around to enable keyboard scrolling.  I selected Ctrl-F to do a "Find in This Page", entering something that I knew would indeed be on the page but below the current (initial) page view.  After the page was scrolled to the search term, keyboard scrolling was enabled.  

Comment 5

[David E. Ross]

On the most recent instance of this problem, I tried wheeled scrolling.  Spinning the wheel on my mouse scrolled the page.  Then clicking the mouse wheel (getting a circle with up and down triangles and a dot in the middle) allowed me to scroll merely by moving the mouse; clicking the mouse wheel again ended that form of scrolling.  

When I was done, neither form of wheel scrolling enabled keyboard scrolling.  However, I think the fact that wheel scrolling itself worked indicated that the focus was indeed on the page.  

Comment 6

[David E. Ross]

It appears that the problem can be reproduced (at least with Windows XP) if some other application takes the focus after SeaMonkey is requested but before SeaMonkey completes its launch.  I seem to be able to create the problem every time by playing solitaire while SeaMonkey is launching.  

Changing the summary.  

Comment 8

[David E. Ross]

Okay, let's try to get this correct.  :(

After further testing, I find that the problem has nothing to do with any other application having focus while SeaMonkey is launching.  Instead, the problem occurs on the first launch of SeaMonkey after a cold boot or a warm reboot.  

Again changing the summary.  

Comment 9

[Tony Mechelynck [:tonymec]]

Tentatively moving to Core::Keyboard_Navigation.

SeaMonkey 1.1 is dead. Does this still happen in some current build (2.0.15, or preferably Sm 2.1 or later)

Comment 10

[David E. Ross]

I have not seen this problem with SM 2.0.14 or 2.1RC1.  

If I see it again, I will reopen this bug report.