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/
20 - Allow webkit:// in URLs.
24 - Minor fixes to manpages.
28 - Makefile: Web extensions and user scripts will be installed.
29 - "enable-developer-extras" is now always set to "TRUE". This enables
31 - WebGL is enabled in WebKit by default these days. lariza's
32 environment variable $LARIZA_ENABLE_EXPERIMENTAL_WEBGL is gone.
35 - User-supplied JavaScript files can be put into
36 ~/.config/lariza/user-scripts. "hints.js" is one such script, it's
37 bundled with the main application, but must be activated manually by
38 copying or linking it to said directory.
42 - We no longer use WebKit's deprecated JavaScript API.
46 - The input bar now shows an indicator for web feeds.
48 The icon used for this purpose is the stock icon called
49 "application-rss+xml-symbolic". It is somewhat "non-standard", i.e.
50 not defined by [0], but appears to be present in many icon themes.
51 Let me know if it doesn't work for you.
53 [0]: https://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html
56 - This is a maintenance release, due to the project moving away from
57 GitHub. No code changes.
61 - Accidentally opening a context menu and then issuing a middle click
62 to open a new tab no longer changes the location of the original tab
63 (fixes #56). (This only happened under certain circumstances.)
67 - Compilation warnings regarding deprecated API calls (GtkAction) have
68 been addressed. Thanks to @jun7 on GitHub!
72 - You can now set the following environment variable to have console
73 output printed to STDOUT: LARIZA_ENABLE_CONSOLE_TO_STDOUT.
77 - The project has been relicensed under the MIT license (more
78 precisely called "Expat License", but everyone calls it "MIT
83 - User input is now properly escaped when used for keyword based
84 searching (fixes #47).
88 - Automatically adding the "file://" prefix didn't work (reliably) if
89 a message was sent to an already running instance.
92 - Autoreloading of crashed web processes has been removed. It doesn't
93 make sense anymore since the switch to webkit's multi-process model.
94 Instead, we now simply announce the crash in the location bar.
95 - Refuse to quit if there are active downloads. The user has to cancel
96 them explicitly. (To improve workflow a little bit, the download
97 manager now also knows a "Mod1 + q" hotkey.)
100 - WebGL can now be enabled by setting an environment variable. This is
101 an experimental feature, though.
105 - As requested by WebKit's API documentation, we now wait for the
106 "ready-to-show" signal after a "create" signal. This fixes crashes
107 after you chose "Open link in new window" from a context menu.
110 - The "search prefix" has been changed from "/" to ":/". This means,
111 in order to search for text in a web page, you now have to enter
112 something like ":/your search term" into the input box.
113 - Lariza now uses WebKit's multi-process model. This means that (most)
114 tabs run as independent processes. If one tab crashes, it should not
116 - The GtkLevelBar to show page loading progress has been removed.
117 Instead, we now use the progress bar which is already included in
118 GtkEntry (the input box). This is mostly a cosmetic change, but it
119 also eliminates some GTK warnings.
122 - An external user-supplied program can be called for the current URI
123 or for hyperlinks/images/videos/audio files.
124 - Lariza will now automatically add a "file://" prefix for local
126 - Hotkeys have been unified. It is now largely irrelevant whether the
127 location bar or the web view has focus.
128 - Lariza can be instructed to write each visited URI to a file.
132 - Lariza no longer reports download progress below 0% or above 100%.
133 (Workaround for what appears to be a WebKit2GTK+ bug.)
136 - We no longer explicitly set the X11 window's class and name. Let
137 GTK+ do this job. The actual class and name should be unchanged,
138 though (WM_CLASS(STRING) = "lariza", "Lariza").
140 This does not affect tabbed which is still run with "-n lariza".
142 This change fixes a GTK+ deprecation warning.
146 - Web extensions are now looked for in ~/.config/lariza/web_extensions.
153 - Except for the default window size, there are no hardcoded pixel
154 values anymore. Should make it a little easier to run lariza on
155 HiDPI screens. (Sorry, not tested, I don't have one.)
158 - New key bindings F2 and F3: Go backward and forward, just like the
159 existing mouse key binds do.
163 - Issue #14: "Keypad enter" now registers as "commit", i.e. "start
164 loading the URL" or "begin searching for search term".
165 - Issue #15: lariza no longer tries to create local file names with
166 directory separators in them when downloading files.
167 - lariza no longer sets the window title to an empty string.
170 - For the sake of consistency, $LARIZA_WEB_EXTENSIONS_DIR has been
174 - Manpages are now available.
176 v15.09 and earlier releases
177 - Sorry, the CHANGES file did not exist back then. Please refer to the