After looking into changing userHTMLBindings.xml and platformHTMLBindings.xml (and trying them in every imaginable location) I'm sure we cannot edit the arrow keys to page up and down as simply as we should be able to (perhaps they are hard coded in this build?).

So I decided to go with xmodmap available at http://maemo.lancode.de
My settings are:
xmodmap -e "keycode 104 = Page_Down"
xmodmap -e "keycode 98 = Page_Up"

The added benefit of changing this globally is better functionality in the rss app. Obviously you will lose the normal up/down function of these keys, but I'm not sure where I would use them anyway (stylus addicted ).

How do you access the about or any ini ?

you type about:config into the url bar of the mozilla based browser

Since I installed the microb browser, the stylus keyboard will pop up in fullscreen mode and then immediately disappear again.

Unfortunately, this happens with Opera too, even if you deinstall the microb browser.

Has anybody found a solution to this problem?

And what if i don't have the chrome directory in my microb directory? Just create it and copy the file there?

Ton.

Yep.

mkdir -p /home/user/.mozilla/microb/chrome/

Anybody know how to make one-touch-install work with microb? I guess its just a mime setting, but what's the mime-type and what application should it be associated with?

Seeing "about:config" under Mozilla on the N800, followed by the snav.enabled preference, gave me some hope that we might be able to page up, page down using the dpad.

Rather than setting "snav.enabled" to false to disable the Spatial Navigation (snav) plugin, or using xmodmap to remap keys, we ought to use snav to do that for us. The documentation on the snav plugin prefs can be found at:
http://www.mozilla.org/access/keyboa...nav_prefs.html
while the KeyEvents can be found at:
http://lxr.mozilla.org/seamonkey/sou...OMKeyEvent.idl

so we *should* be able to set in prefs.js (or "about:config"):

snav.enabled, TRUE
snav.keyCode.modifier, FALSE
snav.keyCode.up, DOM_VK_PAGE_UP
snav.keyCode.down, DOM_VK_PAGE_DOWN

The questions arise on whether the keyEvents have been defined, so I tried both as Strings ("DOM_VK_PAGE_DOWN","DOM_VK_PAGE_UP") and as Ints (33,34) as the decimal values of the hex definitions from KeyEvents.

So far, I've only been successful in scrolling up/down one line at a time. I'm still looking at how well snav has been implemented in the mozilla (firefox3.0a1) beta from http://browser.garage.maemo.org/.

I'd like to see the dpad work "correctly" using snav. Any ideas or help?

One of us is reading that table backwards; I think snav.keyCode.up specifies the keycode that will trigger the snav up action. snav (I think) only jumps around pages by links, buttons, and text boxes, and cannot do simple page up and page down.

I wonder if we could do like this: jump around links only if they are being shown on screen, if not, the up/down button would do line or page up/down.

It´s the behavior found in Opera Mini, and it's very comfortable.

Any ideas?