1 Release history for lariza
5 - lariza now uses native GTK tabs instead of relying on suckless
7 https://www.uninformativ.de/blog/postings/2020-04-26/0/POSTING-en.html
8 - Keyword searches have been removed, as these code paths were
9 unmaintained. See also:
10 https://www.uninformativ.de/blog/postings/2020-05-01/0/POSTING-en.html
11 - The "external URI handler" has been removed, as these code paths
12 were unmaintained. See also:
13 https://www.uninformativ.de/blog/postings/2020-05-01/0/POSTING-en.html
14 - WebKit sandboxing is now enabled. While considered stable, it is a
15 rather new feature. Please report breakages. This also requires you
16 to run at least WebKitGTK 2.26 (released 2019-09-09). See also:
17 https://blogs.gnome.org/mcatanzaro/2020/03/31/sandboxing-webkitgtk-apps/
18 https://www.uninformativ.de/blog/postings/2020-05-04/0/POSTING-en.html
21 - Allow webkit:// in URLs.
25 - Minor fixes to manpages.
29 - Makefile: Web extensions and user scripts will be installed.
30 - "enable-developer-extras" is now always set to "TRUE". This enables
32 - WebGL is enabled in WebKit by default these days. lariza's
33 environment variable $LARIZA_ENABLE_EXPERIMENTAL_WEBGL is gone.
36 - User-supplied JavaScript files can be put into
37 ~/.config/lariza/user-scripts. "hints.js" is one such script, it's
38 bundled with the main application, but must be activated manually by
39 copying or linking it to said directory.
43 - We no longer use WebKit's deprecated JavaScript API.
47 - The input bar now shows an indicator for web feeds.
49 The icon used for this purpose is the stock icon called
50 "application-rss+xml-symbolic". It is somewhat "non-standard", i.e.
51 not defined by [0], but appears to be present in many icon themes.
52 Let me know if it doesn't work for you.
54 [0]: https://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html
57 - This is a maintenance release, due to the project moving away from
58 GitHub. No code changes.
62 - Accidentally opening a context menu and then issuing a middle click
63 to open a new tab no longer changes the location of the original tab
64 (fixes #56). (This only happened under certain circumstances.)
68 - Compilation warnings regarding deprecated API calls (GtkAction) have
69 been addressed. Thanks to @jun7 on GitHub!
73 - You can now set the following environment variable to have console
74 output printed to STDOUT: LARIZA_ENABLE_CONSOLE_TO_STDOUT.
78 - The project has been relicensed under the MIT license (more
79 precisely called "Expat License", but everyone calls it "MIT
84 - User input is now properly escaped when used for keyword based
85 searching (fixes #47).
89 - Automatically adding the "file://" prefix didn't work (reliably) if
90 a message was sent to an already running instance.
93 - Autoreloading of crashed web processes has been removed. It doesn't
94 make sense anymore since the switch to webkit's multi-process model.
95 Instead, we now simply announce the crash in the location bar.
96 - Refuse to quit if there are active downloads. The user has to cancel
97 them explicitly. (To improve workflow a little bit, the download
98 manager now also knows a "Mod1 + q" hotkey.)
101 - WebGL can now be enabled by setting an environment variable. This is
102 an experimental feature, though.
106 - As requested by WebKit's API documentation, we now wait for the
107 "ready-to-show" signal after a "create" signal. This fixes crashes
108 after you chose "Open link in new window" from a context menu.
111 - The "search prefix" has been changed from "/" to ":/". This means,
112 in order to search for text in a web page, you now have to enter
113 something like ":/your search term" into the input box.
114 - Lariza now uses WebKit's multi-process model. This means that (most)
115 tabs run as independent processes. If one tab crashes, it should not
117 - The GtkLevelBar to show page loading progress has been removed.
118 Instead, we now use the progress bar which is already included in
119 GtkEntry (the input box). This is mostly a cosmetic change, but it
120 also eliminates some GTK warnings.
123 - An external user-supplied program can be called for the current URI
124 or for hyperlinks/images/videos/audio files.
125 - Lariza will now automatically add a "file://" prefix for local
127 - Hotkeys have been unified. It is now largely irrelevant whether the
128 location bar or the web view has focus.
129 - Lariza can be instructed to write each visited URI to a file.
133 - Lariza no longer reports download progress below 0% or above 100%.
134 (Workaround for what appears to be a WebKit2GTK+ bug.)
137 - We no longer explicitly set the X11 window's class and name. Let
138 GTK+ do this job. The actual class and name should be unchanged,
139 though (WM_CLASS(STRING) = "lariza", "Lariza").
141 This does not affect tabbed which is still run with "-n lariza".
143 This change fixes a GTK+ deprecation warning.
147 - Web extensions are now looked for in ~/.config/lariza/web_extensions.
154 - Except for the default window size, there are no hardcoded pixel
155 values anymore. Should make it a little easier to run lariza on
156 HiDPI screens. (Sorry, not tested, I don't have one.)
159 - New key bindings F2 and F3: Go backward and forward, just like the
160 existing mouse key binds do.
164 - Issue #14: "Keypad enter" now registers as "commit", i.e. "start
165 loading the URL" or "begin searching for search term".
166 - Issue #15: lariza no longer tries to create local file names with
167 directory separators in them when downloading files.
168 - lariza no longer sets the window title to an empty string.
171 - For the sake of consistency, $LARIZA_WEB_EXTENSIONS_DIR has been
175 - Manpages are now available.
177 v15.09 and earlier releases
178 - Sorry, the CHANGES file did not exist back then. Please refer to the