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