| Age | Commit message (Collapse) | Author |
|---|
|
|
|
The glong type is not always guaranteed to be large enough, e.g., on 32
bit platform. One result is that the scroll percentage is a weird
number. Using explict 64 bit types fixes this.
|
|
- Introduce a scroll_top field in State, similar to scroll_percent but in pixel
- Adjust the webextension to communicate and update scroll_top
- Implement normal_map(), mostly based on vimb-2.12
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Revert "Don't duplicate CFLAGS and CPPFLAGS."
This reverts commit 0cc0db9f7d40fdf9e88f20101a5183e35ba2ea91.
|
|
|
|
The g_variant format 's' will duplicate the memory of the requested
string. Changed this to '&s' to access the serialized data direct so
there is no need to free it.
|
|
Don't put the CPPFLAGS and CFLAGS duplicate to the compiler which lead
to warnings about redefinition of constants on command line like
<command-line>:0:0: warning: "EXTENSIONDIR" redefined
<command-line>:0:0: note: this is the location of the previous
definition
|
|
We use the scrollHeight and the scrollTop of the
document.documentElement. But there are pages where the scrollHeight is
calculated as the same value like the height of the viewport. I can't
identify what causes this issue, but using the document.body
scrollHeight fixes this.
|
|
|
|
|
|
In case a related webview is created. The relation between webextensions
web page and the client in the ui process where mismatched. In fact the
relation was correct, but when a dbus call was fired from ui to
webextension, the webextension used the last created web page to run
javascript in or to focus input fields.
This patch adds the page_id of the web page to the dbus calls that
target a specific web page. So that th webextension can get the right
page by this id to use to answer the call.
Also the communication from webextension to ui lagged this essential
information. So that a click to a editable filed in a related webview
all related instances into input mode switched.
|
|
|
|
Make sure all the scripts we run internally are also evaluated in case
js is disabled.
|
|
|
|
In case the scripts are injected from the ui, they are not processed in
case JavaScript is disabled in vimb. So use the previous dbus logic to
observe dom focus changes and use the script messaging system to inform
the ui process.
|
|
Use script message handler instead of dbus to track for focused editable
elements to switch vimb into input mode or back to normal mode.
|
|
The echo lines where a light alternative to the long compiler options
lines, so there is no real benefit on showing the 'echo' itself.
|
|
This allows to compile with -Wl,--as-needed option which affects only
those libraries written after that option on the command line.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
