summaryrefslogtreecommitdiff
path: root/CHANGES
AgeCommit message (Collapse)Author
2021-01-03"adblock.black" has been renamed to "adblock"Peter Hofmann
2020-08-29Release v20.08Peter Hofmann
2020-08-22Focus c->web_view on new tabsPeter Hofmann
2020-08-16Fix opening links in new tabs (partially)Peter Hofmann
Also, no NULL guard needed for g_free().
2020-07-19Release v20.07Peter Hofmann
2020-07-09Fix build with non-GNU sed, lint variablesPeter Hofmann
2020-05-15Release v20.05Peter Hofmann
2020-05-04CHANGES: Link blog post about sandboxingPeter Hofmann
2020-05-02Allow webkit:// in URLsPeter Hofmann
2020-05-02Enable WebKit sandboxing (and tidy up a bit)Peter Hofmann
2020-04-30CHANGES: Link second blog postPeter Hofmann
2020-04-29Remove external URI handlerPeter Hofmann
2020-04-28Update CHANGESPeter Hofmann
2020-04-22Release v20.04Peter Hofmann
2020-04-17lariza.usage.1: Fix erroneous dots and wrappingPeter Hofmann
2020-03-28Release v20.03Peter Hofmann
2020-03-14CHANGES: Be more precisePeter Hofmann
2020-03-14Move user scriptsPeter Hofmann
This is a more meaningful path.
2020-03-14Update CHANGESPeter Hofmann
2020-03-11WebGL is enabled by defaultPeter Hofmann
2020-03-04Enable WebKit's developer extrasPeter Hofmann
2020-02-22Introduce user-supplied JavaScript filesPeter Hofmann
2019-05-05Release v19.05Peter Hofmann
2019-03-31No longer use WebKit's deprecated JavaScript APIPeter Hofmann
2018-07-29Release v18.07Peter Hofmann
2018-07-29Send bug reports if feed icon doesn't workPeter Hofmann
2018-07-10Update CHANGES and READMEPeter Hofmann
2018-06-24Release v18.06Peter Hofmann
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-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 CHANGES for new env varPeter Hofmann
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-21CHANGES: Mention WebGLPeter Hofmann
CC #36.
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-27Automatically add "file://" prefix for local filesPeter Hofmann
Closes #27.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-25 13:17:08 +0000