40498 - Keyboard listener should be tied to scrollbar

Status: NEW

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

Description

[Rob Kaper]

On a page with a fixed positioned layers of which only one has an overflow
property allowing scrollbars, the keyboard listener for up/down etc should be
tied to that scrollbar.

More general: if there is only one scrollbar (possible) on a page, the keypad
keys allowing one to scroll through a page should be tied to the element with
the scrollbar just like normally they would be tied to the page as a whole.

Check the URL http://capsi.cx/ and thing become more clear ;-), there cannot
possibly be a scrollbar except within the "main" layer, so it should/could be
tied there.

Comment 1

[Asa Dotzler [:asa]]

Sorry for the spam.  New QA Contact for Browser General.  Thanks for your help
Joseph (good luck with the new job) and welcome aboard Doron Rosenberg

Comment 2

[Blake Ross]

Seems like a valid enough issue; if there's only one scrollable viewport on the 
page, navigational keys should be directed there.  reassigning to keyboard 
navigation, but cc'ing trudelle (would this be xp toolkit's issue, since you 
handle key bindings?)

Comment 3

[Blake Ross]

*spam* changing all open or resolved bugs that [e-mail] was the QA 
contact for to [e-mail].  szhu is no longer with netscape, and these 
bugs could lie dormant otherwise.  sorry for spam.

Comment 4

[Chris McAfee]

m21.

Comment 5

[sairuh (rarely reading bugmail)]

adding janc, who might be interested...

Comment 6

[Jeff Yates]

Maybe a related problem!

When a posisioned element (with overflow:scroll CSS property) has focus the 
mouse scroll wheel nor the keyboard will allow you to scroll the element, even 
if it is the only element on the page that is scrollable!!!!

(Build 20001010901 on Win32).

Comment 7

[Chris McAfee]

vishy

Comment 8

[Peter Trudelle]

->bryner

Comment 9

[Brian Ryner (not reading)]

yep, sounds like you've uncovered the root problem behind bug 63663.