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