Keyboards scrolling not working

[atkinsmc]

Scrolling with the keyboard is not working (as in using jklh, or even page-up and page-down). Scrolling with the mouse wheel does work though.

I tried manually entering the command using ": scroll 'vertical' '50'"
This also does nothing.

Please paste the output of uzbl-core --bug-info here:

Commit: v0.9.1-195-g9f81f274
GTK compile: 3.24.12
GTK run: 3.24.12
WebKit compile: 2.26.1
WebKit run: 2.26.1
WebKit2: 1
libsoup compile: 2.68.2
libsoup run: 2.68.2

I ran "uzbl-browser -p" to print out what each command is doing, here is the output:

EVENT [41302] KEY_PRESS '' 'j'
EVENT [41302] COMMAND_EXECUTED scroll 'vertical' '10'
EVENT [41302] VARIABLE_SET keycmd str ''
EVENT [41302] VARIABLE_SET keycmd str ''
EVENT [41302] COMMAND_EXECUTED js 'page' 'string' ' if(0) "#268bd2"; else "#859900"; '
EVENT [41302] COMMAND_EXECUTED js 'page' 'string' ' if(0) "#268bd2"; else "#859900"; '
EVENT [41302] KEY_RELEASE '' 'j'
EVENT [41302] KEY_PRESS '' 'k'
EVENT [41302] COMMAND_EXECUTED scroll 'vertical' '-100'
EVENT [41302] VARIABLE_SET keycmd str ''
EVENT [41302] VARIABLE_SET keycmd str ''
EVENT [41302] COMMAND_EXECUTED js 'page' 'string' ' if(0) "#268bd2"; else "#859900"; '
EVENT [41302] COMMAND_EXECUTED js 'page' 'string' ' if(0) "#268bd2"; else "#859900"; '
EVENT [41302] KEY_RELEASE '' 'k'
EVENT [41302] KEY_PRESS '' 'l'
EVENT [41302] COMMAND_EXECUTED scroll 'horizontal' '100'
EVENT [41302] VARIABLE_SET keycmd str ''
EVENT [41302] VARIABLE_SET keycmd str ''
EVENT [41302] COMMAND_EXECUTED js 'page' 'string' ' if(0) "#268bd2"; else "#859900"; '
EVENT [41302] COMMAND_EXECUTED js 'page' 'string' ' if(0) "#268bd2"; else "#859900"; '
EVENT [41302] KEY_RELEASE '' 'l'
EVENT [41302] KEY_PRESS '' 'h'
EVENT [41302] COMMAND_EXECUTED scroll 'horizontal' '-100'
EVENT [41302] VARIABLE_SET keycmd str ''
EVENT [41302] VARIABLE_SET keycmd str ''
EVENT [41302] COMMAND_EXECUTED js 'page' 'string' ' if(0) "#268bd2"; else "#859900"; '
EVENT [41302] COMMAND_EXECUTED js 'page' 'string' ' if(0) "#268bd2"; else "#859900"; '
EVENT [41302] KEY_RELEASE '' 'h'
EVENT [41302] KEY_PRESS '' Page_Up
EVENT [41302] COMMAND_EXECUTED scroll 'vertical' '-100%'
EVENT [41302] VARIABLE_SET modcmd str ''
EVENT [41302] VARIABLE_SET keycmd str ''
EVENT [41302] COMMAND_EXECUTED js 'page' 'string' ' if(0) "#268bd2"; else "#859900"; '
EVENT [41302] COMMAND_EXECUTED js 'page' 'string' ' if(0) "#268bd2"; else "#859900"; '
EVENT [41302] KEY_RELEASE '' Page_Up
EVENT [41302] VARIABLE_SET modcmd str ''
EVENT [41302] COMMAND_EXECUTED js 'page' 'string' ' if(0) "#268bd2"; else "#859900"; '
EVENT [41302] KEY_PRESS '' Page_Down
EVENT [41302] COMMAND_EXECUTED scroll 'vertical' '100%'
EVENT [41302] VARIABLE_SET modcmd str ''
EVENT [41302] VARIABLE_SET keycmd str ''
EVENT [41302] COMMAND_EXECUTED js 'page' 'string' ' if(0) "#268bd2"; else "#859900"; '
EVENT [41302] COMMAND_EXECUTED js 'page' 'string' ' if(0) "#268bd2"; else "#859900"; '
EVENT [41302] KEY_RELEASE '' Page_Down
`

Is there a specific website which shows the problem?

• This happens for any website

If it is related to a crash on a website, do other WebKit-based browsers
exhibit the same symptoms? Other browsers include surf, midori, jumanji, dwb,
and sugar-browse.

• I installed midori, and scrolling works properly with the arrow keys.

All other key bindings seem to work. This seems like a really nice browser, I would really like to get the scrolling to work so I can use it.

[keis]

Hey @atkinsmc

Scroll command is implemented if you're using the next branch so that should work. However I have not tried that in about a year at this point and there's other stuff that is for sure broken (cookies come to mind).

If you're interested to dig in to it I would start by checking that the web extension is loading correctly it should spit out a message if you set G_DEBUG, however beware you won't exactly end up with a fully functional browser anymore.

[atkinsmc]

Hey @atkinsmc

Scroll command is implemented if you're using the next branch so that should work. However I have not tried that in about a year at this point and there's other stuff that is for sure broken (cookies come to mind).

If you're interested to dig in to it I would start by checking that the web extension is loading correctly it should spit out a message if you set G_DEBUG, however beware you won't exactly end up with a fully functional browser anymore.

I typed ":set G_DEBUG" while in a "uzbl-browser -p" session and did not see anything significant come up. Is this what you mean by "set G_DEBUG"??

[lucabol]

I am seeing the same thing on Arch Linux with package uzbl-next-browser-git

[keis]

There's no development of uzbl going on anymore, maybe it's salvageable but to be honest you are better looking for other options.

I'm surprised it builds at all today.