Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-05-02 | Enable WebKit sandboxing (and tidy up a bit) | Peter Hofmann | |
2020-04-30 | CHANGES: Link second blog post | Peter Hofmann | |
2020-04-29 | Remove external URI handler | Peter Hofmann | |
2020-04-28 | Update CHANGES | Peter Hofmann | |
2020-04-22 | Release v20.04 | Peter Hofmann | |
2020-04-17 | lariza.usage.1: Fix erroneous dots and wrapping | Peter Hofmann | |
2020-03-28 | Release v20.03 | Peter Hofmann | |
2020-03-14 | CHANGES: Be more precise | Peter Hofmann | |
2020-03-14 | Move user scripts | Peter Hofmann | |
This is a more meaningful path. | |||
2020-03-14 | Update CHANGES | Peter Hofmann | |
2020-03-11 | WebGL is enabled by default | Peter Hofmann | |
2020-03-04 | Enable WebKit's developer extras | Peter Hofmann | |
2020-02-22 | Introduce user-supplied JavaScript files | Peter Hofmann | |
2019-05-05 | Release v19.05 | Peter Hofmann | |
2019-03-31 | No longer use WebKit's deprecated JavaScript API | Peter Hofmann | |
2018-07-29 | Release v18.07 | Peter Hofmann | |
2018-07-29 | Send bug reports if feed icon doesn't work | Peter Hofmann | |
2018-07-10 | Update CHANGES and README | Peter Hofmann | |
2018-06-24 | Release v18.06 | Peter Hofmann | |
2018-03-17 | Release v18.03 | Peter Hofmann | |
2018-02-21 | Connect to button release events instead of button press | Peter 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-27 | Release v18.01 | Peter Hofmann | |
2018-01-11 | No longer use GtkAction when constructing the context menu | Peter Hofmann | |
Thanks to @jun7 for helping me out! Closes #54. | |||
2017-11-16 | Release v17.11 | Peter Hofmann | |
2017-10-25 | Update CHANGES for new env var | Peter Hofmann | |
2017-10-18 | Release v17.10 | Peter Hofmann | |
2017-10-07 | Relicense as MIT | Peter Hofmann | |
Closes #53. | |||
2017-07-02 | Release v17.07 | Peter Hofmann | |
2017-05-26 | Add missing call to g_uri_escape_string() | Peter Hofmann | |
Closes #47. | |||
2017-05-21 | Release v17.05 | Peter Hofmann | |
2017-04-21 | CHANGES: Mention WebGL | Peter Hofmann | |
CC #36. | |||
2017-04-08 | Refuse to quit if there are active downloads | Peter Hofmann | |
CC #35. | |||
2017-03-25 | Remove autoreloading of crashed windows | Peter Hofmann | |
CC #32. | |||
2017-03-11 | Call ensure_uri_scheme() before sending message to socket | Peter 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-26 | Release v17.02 | Peter Hofmann | |
2017-02-04 | Optionally write each URI to $LARIZA_HISTORY_FILE | Peter Hofmann | |
2017-01-29 | Remove GtkLevelBar, use bar included in GtkEntry | Peter 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-29 | Switch to multi-process model | Peter 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-29 | CHANGES: Add item about "ready-to-show" signal | Peter Hofmann | |
CC #28. | |||
2017-01-29 | CHANGES: Add item about unified hotkeys | Peter Hofmann | |
2017-01-27 | Automatically add "file://" prefix for local files | Peter Hofmann | |
Closes #27. | |||
2017-01-27 | Change 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-27 | Add external handler to CHANGES | Peter Hofmann | |
Closes #25. | |||
2016-12-24 | Release v16.12 | Peter Hofmann | |
2016-12-14 | Clip return value of webkit_download_get_estimated_progress() to [0, 1] | Peter Hofmann | |
Closes #23. | |||
2016-11-16 | Remove call to gtk_window_set_wmclass() | Peter Hofmann | |
2016-09-03 | Release v16.09 | Peter Hofmann | |
2016-07-30 | Look for web extensions in ~/.config/lariza/web_extensions | Peter 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. | |||
2016-06-26 | Release v16.06 | Peter Hofmann | |
2016-03-19 | Update CHANGES and manpage for new key binds | Peter Hofmann | |