1 Release history for lariza
5 - User input is now properly escaped when used for keyword based
10 - Automatically adding the "file://" prefix didn't work (reliably) if
11 a message was sent to an already running instance.
14 - Autoreloading of crashed web processes has been removed. It doesn't
15 make sense anymore since the switch to webkit's multi-process model.
16 Instead, we now simply announce the crash in the location bar.
17 - Refuse to quit if there are active downloads. The user has to cancel
18 them explicitly. (To improve workflow a little bit, the download
19 manager now also knows a "Mod1 + q" hotkey.)
22 - WebGL can now be enabled by setting an environment variable. This is
23 an experimental feature, though.
27 - As requested by WebKit's API documentation, we now wait for the
28 "ready-to-show" signal after a "create" signal. This fixes crashes
29 after you chose "Open link in new window" from a context menu.
32 - The "search prefix" has been changed from "/" to ":/". This means,
33 in order to search for text in a web page, you now have to enter
34 something like ":/your search term" into the input box.
35 - Lariza now uses WebKit's multi-process model. This means that (most)
36 tabs run as independent processes. If one tab crashes, it should not
38 - The GtkLevelBar to show page loading progress has been removed.
39 Instead, we now use the progress bar which is already included in
40 GtkEntry (the input box). This is mostly a cosmetic change, but it
41 also eliminates some GTK warnings.
44 - An external user-supplied program can be called for the current URI
45 or for hyperlinks/images/videos/audio files.
46 - Lariza will now automatically add a "file://" prefix for local
48 - Hotkeys have been unified. It is now largely irrelevant whether the
49 location bar or the web view has focus.
50 - Lariza can be instructed to write each visited URI to a file.
54 - Lariza no longer reports download progress below 0% or above 100%.
55 (Workaround for what appears to be a WebKit2GTK+ bug.)
58 - We no longer explicitly set the X11 window's class and name. Let
59 GTK+ do this job. The actual class and name should be unchanged,
60 though (WM_CLASS(STRING) = "lariza", "Lariza").
62 This does not affect tabbed which is still run with "-n lariza".
64 This change fixes a GTK+ deprecation warning.
68 - Web extensions are now looked for in ~/.config/lariza/web_extensions.
75 - Except for the default window size, there are no hardcoded pixel
76 values anymore. Should make it a little easier to run lariza on
77 HiDPI screens. (Sorry, not tested, I don't have one.)
80 - New key bindings F2 and F3: Go backward and forward, just like the
81 existing mouse key binds do.
85 - Issue #14: "Keypad enter" now registers as "commit", i.e. "start
86 loading the URL" or "begin searching for search term".
87 - Issue #15: lariza no longer tries to create local file names with
88 directory separators in them when downloading files.
89 - lariza no longer sets the window title to an empty string.
92 - For the sake of consistency, $LARIZA_WEB_EXTENSIONS_DIR has been
96 - Manpages are now available.
98 v15.09 and earlier releases
99 - Sorry, the CHANGES file did not exist back then. Please refer to the