1 Release history for lariza
5 - "enable-developer-extras" is now always set to "TRUE". This enables
9 - User-supplied JavaScript files can be put into
10 ~/.config/lariza/scripts.
14 - We no longer use WebKit's deprecated JavaScript API.
18 - The input bar now shows an indicator for web feeds.
20 The icon used for this purpose is the stock icon called
21 "application-rss+xml-symbolic". It is somewhat "non-standard", i.e.
22 not defined by [0], but appears to be present in many icon themes.
23 Let me know if it doesn't work for you.
25 [0]: https://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html
28 - This is a maintenance release, due to the project moving away from
29 GitHub. No code changes.
33 - Accidentally opening a context menu and then issuing a middle click
34 to open a new tab no longer changes the location of the original tab
35 (fixes #56). (This only happened under certain circumstances.)
39 - Compilation warnings regarding deprecated API calls (GtkAction) have
40 been addressed. Thanks to @jun7 on GitHub!
44 - You can now set the following environment variable to have console
45 output printed to STDOUT: LARIZA_ENABLE_CONSOLE_TO_STDOUT.
49 - The project has been relicensed under the MIT license (more
50 precisely called "Expat License", but everyone calls it "MIT
55 - User input is now properly escaped when used for keyword based
56 searching (fixes #47).
60 - Automatically adding the "file://" prefix didn't work (reliably) if
61 a message was sent to an already running instance.
64 - Autoreloading of crashed web processes has been removed. It doesn't
65 make sense anymore since the switch to webkit's multi-process model.
66 Instead, we now simply announce the crash in the location bar.
67 - Refuse to quit if there are active downloads. The user has to cancel
68 them explicitly. (To improve workflow a little bit, the download
69 manager now also knows a "Mod1 + q" hotkey.)
72 - WebGL can now be enabled by setting an environment variable. This is
73 an experimental feature, though.
77 - As requested by WebKit's API documentation, we now wait for the
78 "ready-to-show" signal after a "create" signal. This fixes crashes
79 after you chose "Open link in new window" from a context menu.
82 - The "search prefix" has been changed from "/" to ":/". This means,
83 in order to search for text in a web page, you now have to enter
84 something like ":/your search term" into the input box.
85 - Lariza now uses WebKit's multi-process model. This means that (most)
86 tabs run as independent processes. If one tab crashes, it should not
88 - The GtkLevelBar to show page loading progress has been removed.
89 Instead, we now use the progress bar which is already included in
90 GtkEntry (the input box). This is mostly a cosmetic change, but it
91 also eliminates some GTK warnings.
94 - An external user-supplied program can be called for the current URI
95 or for hyperlinks/images/videos/audio files.
96 - Lariza will now automatically add a "file://" prefix for local
98 - Hotkeys have been unified. It is now largely irrelevant whether the
99 location bar or the web view has focus.
100 - Lariza can be instructed to write each visited URI to a file.
104 - Lariza no longer reports download progress below 0% or above 100%.
105 (Workaround for what appears to be a WebKit2GTK+ bug.)
108 - We no longer explicitly set the X11 window's class and name. Let
109 GTK+ do this job. The actual class and name should be unchanged,
110 though (WM_CLASS(STRING) = "lariza", "Lariza").
112 This does not affect tabbed which is still run with "-n lariza".
114 This change fixes a GTK+ deprecation warning.
118 - Web extensions are now looked for in ~/.config/lariza/web_extensions.
125 - Except for the default window size, there are no hardcoded pixel
126 values anymore. Should make it a little easier to run lariza on
127 HiDPI screens. (Sorry, not tested, I don't have one.)
130 - New key bindings F2 and F3: Go backward and forward, just like the
131 existing mouse key binds do.
135 - Issue #14: "Keypad enter" now registers as "commit", i.e. "start
136 loading the URL" or "begin searching for search term".
137 - Issue #15: lariza no longer tries to create local file names with
138 directory separators in them when downloading files.
139 - lariza no longer sets the window title to an empty string.
142 - For the sake of consistency, $LARIZA_WEB_EXTENSIONS_DIR has been
146 - Manpages are now available.
148 v15.09 and earlier releases
149 - Sorry, the CHANGES file did not exist back then. Please refer to the