summaryrefslogtreecommitdiff
path: root/config.def.h
diff options
context:
space:
mode:
authorQuentin Rameau <quinq@fifth.space>2016-03-02 14:29:21 +0100
committerQuentin Rameau <quinq@fifth.space>2016-03-02 14:46:14 +0100
commitaf7522006b2aa1b92081a474f831df52d6d9ff13 (patch)
tree4d643ca955d76c69af75de5b0e73f351753ae351 /config.def.h
parent50befe4a9586f7ef29a00ae78e7580dfe16a48df (diff)
downloadsurf-af7522006b2aa1b92081a474f831df52d6d9ff13.tar.gz
surf-af7522006b2aa1b92081a474f831df52d6d9ff13.tar.bz2
surf-af7522006b2aa1b92081a474f831df52d6d9ff13.zip
Get rid of JavaScript for scrolling in views
This is still a hack, until WebKitGTK gives us a more practical and stable way to do that. Manipulating directly the DOM inside a webextension is a pain and only usable with unstable API atm.
Diffstat (limited to 'config.def.h')
-rw-r--r--config.def.h17
1 files changed, 10 insertions, 7 deletions
diff --git a/config.def.h b/config.def.h
index 4f6d655..aca8f59 100644
--- a/config.def.h
+++ b/config.def.h
@@ -109,13 +109,16 @@ static Key keys[] = {
{ MODKEY, GDK_KEY_l, navigate, { .i = +1 } },
{ MODKEY, GDK_KEY_h, navigate, { .i = -1 } },
- /* in page % */
- { MODKEY, GDK_KEY_j, scroll_v, { .i = +10 } },
- { MODKEY, GDK_KEY_k, scroll_v, { .i = -10 } },
- { MODKEY, GDK_KEY_b, scroll_v, { .i = -50 } },
- { MODKEY, GDK_KEY_space, scroll_v, { .i = +50 } },
- { MODKEY, GDK_KEY_i, scroll_h, { .i = +10 } },
- { MODKEY, GDK_KEY_u, scroll_h, { .i = -10 } },
+ /* Currently we have to use scrolling steps that WebKit2GTK+ gives us
+ * d: step down, u: step up, r: step right, l:step left
+ * D: page down, U: page up */
+ { MODKEY, GDK_KEY_j, scroll, { .i = 'd' } },
+ { MODKEY, GDK_KEY_k, scroll, { .i = 'u' } },
+ { MODKEY, GDK_KEY_b, scroll, { .i = 'U' } },
+ { MODKEY, GDK_KEY_space, scroll, { .i = 'D' } },
+ { MODKEY, GDK_KEY_i, scroll, { .i = 'r' } },
+ { MODKEY, GDK_KEY_u, scroll, { .i = 'l' } },
+
{ MODKEY|GDK_SHIFT_MASK, GDK_KEY_j, zoom, { .i = -1 } },
{ MODKEY|GDK_SHIFT_MASK, GDK_KEY_k, zoom, { .i = +1 } },