1 Release history for lariza
4 - This is a maintenance release, due to the project moving away from
5 GitHub. No code changes.
9 - Accidentally opening a context menu and then issuing a middle click
10 to open a new tab no longer changes the location of the original tab
11 (fixes #56). (This only happened under certain circumstances.)
15 - Compilation warnings regarding deprecated API calls (GtkAction) have
16 been addressed. Thanks to @jun7 on GitHub!
20 - You can now set the following environment variable to have console
21 output printed to STDOUT: LARIZA_ENABLE_CONSOLE_TO_STDOUT.
25 - The project has been relicensed under the MIT license (more
26 precisely called "Expat License", but everyone calls it "MIT
31 - User input is now properly escaped when used for keyword based
32 searching (fixes #47).
36 - Automatically adding the "file://" prefix didn't work (reliably) if
37 a message was sent to an already running instance.
40 - Autoreloading of crashed web processes has been removed. It doesn't
41 make sense anymore since the switch to webkit's multi-process model.
42 Instead, we now simply announce the crash in the location bar.
43 - Refuse to quit if there are active downloads. The user has to cancel
44 them explicitly. (To improve workflow a little bit, the download
45 manager now also knows a "Mod1 + q" hotkey.)
48 - WebGL can now be enabled by setting an environment variable. This is
49 an experimental feature, though.
53 - As requested by WebKit's API documentation, we now wait for the
54 "ready-to-show" signal after a "create" signal. This fixes crashes
55 after you chose "Open link in new window" from a context menu.
58 - The "search prefix" has been changed from "/" to ":/". This means,
59 in order to search for text in a web page, you now have to enter
60 something like ":/your search term" into the input box.
61 - Lariza now uses WebKit's multi-process model. This means that (most)
62 tabs run as independent processes. If one tab crashes, it should not
64 - The GtkLevelBar to show page loading progress has been removed.
65 Instead, we now use the progress bar which is already included in
66 GtkEntry (the input box). This is mostly a cosmetic change, but it
67 also eliminates some GTK warnings.
70 - An external user-supplied program can be called for the current URI
71 or for hyperlinks/images/videos/audio files.
72 - Lariza will now automatically add a "file://" prefix for local
74 - Hotkeys have been unified. It is now largely irrelevant whether the
75 location bar or the web view has focus.
76 - Lariza can be instructed to write each visited URI to a file.
80 - Lariza no longer reports download progress below 0% or above 100%.
81 (Workaround for what appears to be a WebKit2GTK+ bug.)
84 - We no longer explicitly set the X11 window's class and name. Let
85 GTK+ do this job. The actual class and name should be unchanged,
86 though (WM_CLASS(STRING) = "lariza", "Lariza").
88 This does not affect tabbed which is still run with "-n lariza".
90 This change fixes a GTK+ deprecation warning.
94 - Web extensions are now looked for in ~/.config/lariza/web_extensions.
101 - Except for the default window size, there are no hardcoded pixel
102 values anymore. Should make it a little easier to run lariza on
103 HiDPI screens. (Sorry, not tested, I don't have one.)
106 - New key bindings F2 and F3: Go backward and forward, just like the
107 existing mouse key binds do.
111 - Issue #14: "Keypad enter" now registers as "commit", i.e. "start
112 loading the URL" or "begin searching for search term".
113 - Issue #15: lariza no longer tries to create local file names with
114 directory separators in them when downloading files.
115 - lariza no longer sets the window title to an empty string.
118 - For the sake of consistency, $LARIZA_WEB_EXTENSIONS_DIR has been
122 - Manpages are now available.
124 v15.09 and earlier releases
125 - Sorry, the CHANGES file did not exist back then. Please refer to the