Separating a process in WebKit2 has some advantages, but it also complicates many things. I believe that scrolling is one of these things: this happens in the web process, because now the scroll bars are handled by webkit and not the Gtk widget. The same should be considered when working with touch control: it is partially performed in the web process. Carlos Garcia Campos wrote a blog post about using WebKitWebExtension to help with this. Note that design has many implications for your code: part of the code will work in a completely different process.
, , :
, DOM API, DOMDOMWindow.scroll*. DOMDOMWindow. WebExtension, -, , WebPage. WebPage.get_dom_document() DOMDocument, DOMDocument.get_default_view() DOMDOMWindow, .
DOM API Mozilla, , , spartan WebKit-GTK-DOM.
, , # webkitgtk + IRC- Freenode, , , ...