| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
Regroup all toggles in an enum and handle them with a unique function
via a switch. That lets us take different actions for each toggle.
Add a frame flatenning and a dns preteching options.
|
| |
|
|
|
|
|
| |
Slightly new behaviour: searching again for the same string (via MOD+/)
resets the search (ie restarts search from document top).
Searching for an empty string stops the search (ie all highlights are
removed).
|
| | |
|
| | |
|
| |
|
|
|
| |
We do not have access to scrollbars and will have to manipulate DOM to
do that.
|
| |
|
|
|
|
| |
In fact, we have a scrolling handle ersatz for now using JavaScript
calls as we don't have access anymore to scrollbars.
We'll have to manipulate the DOM directly (later).
|
| |
|
|
|
| |
The inspector is now easily manageable via API, there's no need for
keeping its state in the Client.
|
| | |
|
| |
|
|
|
| |
We can directly use style file pointers instead of using temporary
string pointers.
|
| |
|
|
|
| |
We can't anymore pass a simple path to a stylefile, we have to read the
entire file to create a stylesheet and apply it to the view.
|
| |
|
|
| |
Replace linkhover with target uri and add some comments
|
| |
|
|
|
| |
And handle c->fullscreen value in winevent(). This way we keep track of
fullscreen state even if we did not directly initiate the fullscreen.
|
| |
|
|
|
| |
All GtkWidget events have the same function prototype with the generic
GdkEvent as parameter. This will let us handle everything in the switch.
|
| |
|
|
|
| |
Removed eval(), evalscript() is now sufficient and can directly execute
passed JavaScript string.
|
| |
|
|
|
|
| |
The “window-object-cleared” signal is not directly accessible for
specific WebViews now. We'll have to use an Extension or rewrite the
JavaScript running functions.
|
| |
|
|
| |
Move there window creation from showview().
|
| |
|
|
|
| |
Simply call gtk_widget_destroy() on the window. Then GtkWindow closing
process will take care of the rest.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Those were added because “right click menu to copy the link URI will now
work” (would not work) in 2013. It's been a while since that works without
intervention.
|
| |
|
|
|
|
|
| |
Use the current hit test (c->mousepos) to determine where the mouse
pointer is.
It is possible to link an action to a click and still propagate the
event after that by setting the “stop event” parameter of a Button to 0.
|
| |
|
|
|
| |
Attach to download requests on WebKitContext, this way we can easily
manage all types of downloads (coming from views or not).
|
| | |
|
| |
|
|
|
|
|
| |
Keep a GTlsCertificateFlags in Client for TLS errors.
If we don't use a ssl connection, set it to a value greater than maximum
error flag value (which is G_TLS_CERTIFICATE_VALIDATE_ALL for all
possible errors).
|
| | |
|
| |
|
|
|
|
| |
Now all the requests are triggered by one signal.
We then handle each type, resource download, navigation, newwindow, in
separate functions.
|
| |
|
|
|
| |
We can now perform some filtering before opening a new view (window)
when requested by JavaScript (either random or by a click).
|
| |
|
|
|
| |
The permission-request signal can now ask for than a geolocation
authorisation (though we only handle that for now).
|
| |
|
|
|
|
|
| |
The “linkhover” can now be more than a simple link (image, video, etc.).
As we can't anymore perform a hit test when we want, we have to keep the
last known hit test to be able to know where the mouse is on the next
click event.
|
| |
|
|
| |
These relate more to the position of the pointer when an event occurs.
|
| |
|
|
| |
Do not copy title strings, just carry over the const pointer.
|
| |
|
|
|
| |
Most all the settings and callbacks are set before view creation.
Create a related view (with inherited settings) if asked to.
|
| |
|
|
|
|
| |
View creation is now done in a separate function.
That helps identifying the workflow and let us easily carry related
view (client) when asked by the WebKit for a new one.
|
| |
|
|
|
| |
Only show the window when and if the view is ready.
Move all the window rendering there.
|
| |
|
|
|
| |
Use one WebKitWebProcess per view instead of one for all views.
More information in the API documentation.
|
| | |
|
| |
|
|
|
|
|
| |
We don't have access anymore to the scrolling process and have to rely
entirely on WebKit.
We could be able to manage scrolling and bars directly by manipulating
the DOM via a WebKitExtension. To be continued…
|
| | |
|
| | |
|
| |
|
|
| |
Remove all soup cookie handling and use provided interface.
|
| |
|
|
|
| |
WebKit2GTK doesn't provide a direct way to view source anymore, we'll
have to do that ourselves with a GtkSourceView if we still need that.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: Christoph Lohmann <20h@r-36.net>
|
| |
|
|
|
|
|
| |
The enablestyles configuration variable and parameter flag manages the
global application of styles, not just the site-specific styles.
Signed-off-by: Christoph Lohmann <20h@r-36.net>
|
| |
|
|
|
|
| |
Do not try to show the inspector window when the inspector is disabled.
Signed-off-by: Christoph Lohmann <20h@r-36.net>
|
| |
|
|
| |
Signed-off-by: Christoph Lohmann <20h@r-36.net>
|
| |
|
|
|
|
|
| |
Handle the fullscreen in a more consistent way with other options:
-f disables fullscreen while -F enables fullscreen.
Signed-off-by: Christoph Lohmann <20h@r-36.net>
|
Quentin Rameau
Quentin Rameau
