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.

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

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?)

*spam* changing all open or resolved bugs that szhu@netscape.com was the QA contact for to sairuh@netscape.com. szhu is no longer with netscape, and these bugs could lie dormant otherwise. sorry for spam.

m21.

adding janc, who might be interested...

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).

vishy

->bryner

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