Bug 2423 – dpad configuration needed

Bug 2423 - dpad configuration needed


Summary:	dpad configuration needed

Status:	RESOLVED WONTFIX

Product:	Browser
Component:	User interface
Version:	4.0
Platform:	All All

Importance:	Medium enhancement (vote)
Target Milestone:	4.0
Assigned To:	unassigned
QA Contact:	browser-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2007-11-29 20:53 UTC by phi
Modified:	2007-12-06 02:04 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description phi (reporter) 2007-11-29 20:53:33 UTC

STEPS TO REPRODUCE THE PROBLEM:There is no way to configure the directional pad
(dpad) so a user can set scrolling/paging/navigating for each direction.  This
affects all microB browsers on the 770/n800/and possibly n810. originally with
the opera browser, these configurations were handled in the
/home/user/.opera/input.ini file

EXPECTED OUTCOME: user configuration panel for dpad for microB

ACTUAL OUTCOME:

REPRODUCIBILITY: always
(always/sometimes/once)

EXTRA SOFTWARE INSTALLED:

OTHER COMMENTS:

Comment 1 timeless 2007-11-29 21:59:55 UTC

this was never a documented feature and we do not intend to implement it.

sorry.

you're free to see about writing an extension that makes you happy.

Comment 2 Dave Blank 2007-11-29 23:16:37 UTC

I would think it would be possible to change key mappings in
/usr/lib/microb-engine/chrome/toolkit/content/global/platformHTMLBindings.xml ?

I tried to change
      <handler event="keypress" keycode="VK_UP" command="cmd_scrollLineUp" />   
      <handler event="keypress" keycode="VK_DOWN" command="cmd_scrollLineDown"
/>                              
to:
      <handler event="keypress" keycode="VK_UP" command="cmd_movePageUp"/>      
      <handler event="keypress" keycode="VK_DOWN" command="cmd_movePageDown"/>

I expected up and down to act as page up / page down afterwards, but had no
such luck.

It looks like platformHTMLBindings.xml is at least opened according to strace,
but why load if it's ignoring key bindings?

Or am I just doing this wrong? :)

Comment 3 timeless 2007-11-30 08:59:26 UTC

try setting about:config?sprefname=snav.enabled to false first.

the spatial navigation extension eats keys first before gecko gets them.

Comment 4 Dave Blank 2007-11-30 09:12:19 UTC

Excellent!

This appears to have done the trick.

Thanks for the help :)

Comment 5 Dave Blank 2007-11-30 20:16:05 UTC

Here's the full workaround:

Close any running browsers.

edit
/usr/lib/microb-engine/chrome/toolkit/content/global/platformHTMLBindings.xml

change
<handler event="keypress" keycode="VK_UP" command="cmd_scrollLineUp" />
<handler event="keypress" keycode="VK_DOWN" command="cmd_scrollLineDown" />
to:
<handler event="keypress" keycode="VK_UP" command="cmd_movePageUp"/>
<handler event="keypress" keycode="VK_DOWN" command="cmd_movePageDown"/>

edit
~/.mozilla/microb/prefs.js

change
user_pref("snav.enabled", true);
to:
user_pref("snav.enabled", false);

Restart browser

Comment 6 Ryan Abel maemo.org

2007-12-05 21:53:11 UTC

Yes, this works perfectly for me, too. Excellent, thanks!

Comment 7 timeless 2007-12-06 02:04:28 UTC

http://timeless.justdave.net/maemo/microb-pageupdown-0.1.deb

you'll need to make sure the browser isn't running when you install this.