summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2018-03-17Release v18.03Peter Hofmann
2018-02-21Connect to button release events instead of button pressPeter Hofmann
By default, WebKit only responds to release events. The old code listened for press events. That's probably not the right way to do things. We should properly "override" the release events. Closes #56.
2018-01-27Release v18.01Peter Hofmann
2018-01-13LICENSE: Year bumpPeter Hofmann
2018-01-13Remove "whacky" commentPeter Hofmann
I was probably thinking about multibyte encodings when I left that note, but we explicitly check whether the first two bytes are ':' and '/', so it's fine to skip them.
2018-01-13Remove irrelevant parameter namePeter Hofmann
2018-01-13Use full signature for external_handler_runPeter Hofmann
Yes, this needs the two void casts to make the compiler not complain about unused parameters, but I think "explicit is better than implicit" here. And none of the other callbacks use this trick.
2018-01-11No longer use GtkAction when constructing the context menuPeter Hofmann
Thanks to @jun7 for helping me out! Closes #54.
2017-11-16Release v17.11Peter Hofmann
2017-10-25Update LICENSE for fvghPeter Hofmann
2017-10-25Update CHANGES for new env varPeter Hofmann
2017-10-25Merge pull request #55 from fvgh/console_to_stdoutPeter Hofmann
Support WebKit "enable-write-console-messages-to-stdout"
2017-10-24Support WebKit "enable-write-console-messages-to-stdout" via env-variable.Frank Vennemeyer
2017-10-18Release v17.10Peter Hofmann
2017-10-07Relicense as MITPeter Hofmann
Closes #53.
2017-07-02Release v17.07Peter Hofmann
2017-05-26Add missing call to g_uri_escape_string()Peter Hofmann
Closes #47.
2017-05-21Release v17.05Peter Hofmann
2017-04-29Add PATCHESPeter Hofmann
2017-04-27Code style nitpickingPeter Hofmann
2017-04-27Merge pull request #39 from onodera-punpun/loadvain
Hide progress bar once the webpage has finished loading
2017-04-26Hide progress bar once the webpage has finished loadingCamille Scholtz
2017-04-21CHANGES: Mention WebGLPeter Hofmann
CC #36.
2017-04-21Add option to enable WebGLPeter Hofmann
CC #36.
2017-04-08README: Remove note about Flash and JavaPeter Hofmann
This was relevant some years ago. Today, Flash is dying quickly and I don't even care about Java anymore. On top of that, support for these two things never was a feature of lariza but of WebKit.
2017-04-08Minor nitpickingPeter Hofmann
2017-04-08Refuse to quit if there are active downloadsPeter Hofmann
CC #35.
2017-03-25Remove autoreloading of crashed windowsPeter Hofmann
CC #32.
2017-03-11Call ensure_uri_scheme() before sending message to socketPeter Hofmann
The main process and the process that sends the message might have different working directories. As a result, the main process might not be able to detect "foo.html" as a file when called as "lariza foo.html".
2017-02-26Release v17.02Peter Hofmann
2017-02-04Optionally write each URI to $LARIZA_HISTORY_FILEPeter Hofmann
2017-01-29Remove GtkLevelBar, use bar included in GtkEntryPeter Hofmann
I was still seeing this warning whenever the GtkLevelBar was set to a value of 0: Negative content width -2 (allocation 0, extents 1x1) while allocating gadget (node block, owner GtkLevelBar) This happens even in a minimal test program: #include <gtk/gtk.h> int main(int argc, char **argv) { GtkWidget *win, *progress; gtk_init(&argc, &argv); win = gtk_window_new(GTK_WINDOW_TOPLEVEL); progress = gtk_level_bar_new(); gtk_level_bar_set_value(GTK_LEVEL_BAR(progress), 0); gtk_container_add(GTK_CONTAINER(win), progress); gtk_widget_show_all(win); gtk_main(); } It would appear that it's illegal to call gtk_level_bar_set_value() with a value of 0. Or, and that's just as likely, I don't understand how a GtkLevelBar is supposed to work. You don't even have to call gtk_level_bar_set_value() at all, since 0 is the default value of such a bar. All of this doesn't really matter, though, since GtkEntry has a built-in progress bar that we can use. CC #20.
2017-01-29Switch to multi-process modelPeter Hofmann
I think this is a good thing to do in any case. One crashed tab/window should no longer be able to crash all other tabs as well. CC #28: This change also appears to be a workaround for scenario number two (`Alt+e` can crash WebKit/lariza).
2017-01-29CHANGES: Add item about "ready-to-show" signalPeter Hofmann
CC #28.
2017-01-29CHANGES: Add item about unified hotkeysPeter Hofmann
2017-01-29Fixup for 82d5f9e: Search prefix is ":/" nowPeter Hofmann
2017-01-29Deduplicate shared code in key handlersPeter Hofmann
2017-01-29Wait for "ready-to-show" signal after a "create" signalPeter Hofmann
CC #28.
2017-01-28s/malloc/callocPeter Hofmann
2017-01-27Automatically add "file://" prefix for local filesPeter Hofmann
Closes #27.
2017-01-27Change search prefix to ":/"Peter Hofmann
I want to change ensure_uri_scheme() so it automatically adds "file://" if we're dealing with a valid local file path. However, this clashes with "/" as a search prefix. CC #27.
2017-01-27Merge branch 'external-handler'Peter Hofmann
2017-01-27Add external handler to CHANGESPeter Hofmann
Closes #25.
2017-01-27Add documentation about URI handler to man pagesPeter Hofmann
2017-01-27Add launching of an external script for selected URLsPeter Hofmann
2016-12-24Release v16.12Peter Hofmann
2016-12-14Clip return value of webkit_download_get_estimated_progress() to [0, 1]Peter Hofmann
Closes #23.
2016-11-16Remove call to gtk_window_set_wmclass()Peter Hofmann
2016-09-03Release v16.09Peter Hofmann
2016-07-30Look for web extensions in ~/.config/lariza/web_extensionsPeter Hofmann
~/.local/share isn't really an appropriate place because it's meant to contain "data", possibly written by the application. Usually, lariza's web extensions (.so files) are not placed in your home directory anyway. Instead, they are installed somewhere in /usr. The home directory only contains symlinks. So, in a way, those symlinks can be considered "configuration items". Hence, ~/.config is where they should live.
generated by cgit v1.2.3 (git 2.39.1) at 2025-02-18 02:56:36 +0000