summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-05-05Release v19.05Peter Hofmann
2019-05-05LICENSE: Bump yearPeter Hofmann
2019-03-31No longer use WebKit's deprecated JavaScript APIPeter Hofmann
2019-03-17Add BUGS: Mention currently deprecated functionsPeter Hofmann
2018-07-29Release v18.07Peter Hofmann
2018-07-29Send bug reports if feed icon doesn't workPeter Hofmann
2018-07-29Fix typoPeter Hofmann
2018-07-10Get rid of those ugly global variablesPeter Hofmann
2018-07-10Simplify: Merge feed_icon() into grab_feeds_finished()Peter Hofmann
2018-07-10README: Remove the "1000 lines of code" statementPeter Hofmann
We've already exceeded that limit and it's not a good measurement for code quality anyway (not implying that this code is of extraordinarily good quality), so let's just get rid of it.
2018-07-10Update CHANGES and READMEPeter Hofmann
2018-07-10Workaround for graphical padding artifactPeter Hofmann
2018-07-10feed_html_header: Default to UTF-8Peter Hofmann
2018-07-10Indicate RSS/Atom feeds on web sitesPeter Hofmann
2018-06-24Release v18.06Peter Hofmann
2018-06-08PATCHES: Remove GitHub linkPeter Hofmann
2018-06-08README: Add new headerPeter 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-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).
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-29 11:01:28 +0000