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