Change Log | qutebrowser

Support for Python 3.8 is dropped, and Python 3.9 is now required. (#8325)

Support for macOS 12 Monterey is now dropped, and binaries will be built on macOS 13 Ventura. (#8327)

When using the installer on Windows 10, build 1809 or newer is now required (previous versions required 1607 or newer, but that’s not officialy supported by Qt upstream). (#8336)

Windows/macOS binaries are now built with Qt 6.8.1. (#8242)

Based on Chromium 122.0.6261.171

With security patches up to 131.0.6778.70

Windows/macOS binaries are now using Python 3.13. (#8205)

The .desktop file now also declares qutebrowser as a valid viewer for image/webp. (#8340)

Updated mimetype information for getting a suitable extension when downloading a data: URL.

The content.javascript.clipboard setting now defaults to "ask", which on Qt 6.8+ will prompt the user to grant clipboard access. On older Qt versions, this is still equivalent to "none" and needs to be set manually. (#8348)

If a XHR request made via JS sets a custom Accept-Language header, it now correctly has precedence over the global content.headers.accept_language setting (but not per-domain overrides). This fixes subtle JS issues on websites that rely on the custom header being sent for those requests, and e.g. block the requests server-side otherwise. (#8370)

Our packaging scripts now prefer the "legacy"/"for older browsers" PDF.js build as their normal release only supports the latest Chromium version and might break in qutebrowser on updates. Note to packagers: If there’s a PDF.js package in your distribution as an (optional) qutebrowser dependency, consider also switching to this variant (same code, built differently).

Crash with recent Jinja/Markupsafe versions when viewing a finished userscript (or potentially editor) process via :process.

scripts/open_url_in_instance.sh now avoids echo -n, thus running correctly on POSIX sh. (#8409)

Added a workaround for a bogus QtWebEngine warning about missing spell checking dictionaries. (#8330)

Updated the workaround for Google sign-in issues.

Added the qt.workarounds.disable_hangouts_extension setting, for disabling the Google Hangouts extension built into Chromium/QtWebEngine.

Failed end2end tests will now save screenshots of the browser window when run under xvfb (the default on linux). Screenshots will be under $TEMP/pytest-current/pytest-screenshots/ or attached to the GitHub actions run as an artifact. (#7625)

Support for macOS 11 Big Sur is dropped. Binaries are now built on macOS 12 Monterey and are unlikely to still run on older macOS versions.

The qute-pass userscript now has better support for internationalized domain names when using the pass backend - both domain names and secret paths are normalized before comparing (#8133)

Ignored URL query parameters (via url.yank_ignored_parameters) are now respected when yanking any URL (for example, through hints with hint links yank). The {url:yank} substitution has also been added as a version of {url} that respects ignored URL query parameters. (#7879)

Windows and macOS releases now bundle Qt 6.7.3, which includes security fixes up to Chromium 129.0.6668.58.

A minor memory leak of QItemSelectionModels triggered by closing the completion dialog has been resolved. (#7950)

The link to the chrome URL match pattern documentation in our settings docs now loads a live page again. (#8268)

A rare crash when on Qt 6, a renderer process terminates with an unknown termination reason.

Updated the workaround for Google sign-in issues.

There is now a separate macOS release built for Apple Silicon. A Universal Binary might follow with a later release.

Windows and macOS releases now bundle Qt 6.7.2, which includes security fixes up to Chromium 125.0.6422.142.

When the selected Qt wrapper is unavailable, qutebrowser now again shows a GUI error message instead of only an exception in the terminal.

This will be the last feature release supporting macOS 11 Big Sur. Starting with qutebrowser v3.3.0, macOS 12 Monterey will be the oldest supported version.

When qutebrowser receives a SIGHUP it will now reload any config.py file in use (same as the :config-source command does). (#8108)

The Chromium security patch version is now shown in the backend string in --version and :version. This reflects the latest Chromium version that security fixes have been backported to the base QtWebEngine version from. (#7187)

Windows and macOS releases now ship with Qt 6.7.1, which is based on Chromium 118.0.5993.220 with security patches up to 124.0.6367.202.

With QtWebEngine 6.7+, the colors.webpage.darkmode.enabled setting can now be changed at runtime and supports URL patterns (#8182).

A few more completions will now match search terms in any order: :quickmark-*, :bookmark-*, :tab-take and :tab-select (for the quick and bookmark categories). (#7955)

Elements with an ARIA role="switch" now get hints (toggle switches like e.g. on cookie banners).

The tor_identity userscript now validates that the -c|--control-port argument value is an int. (#8162)

input.insert_mode.auto_load sometimes not triggering due to a race condition. (#8145)

Worked around qutebrowser quitting when closing a KDE file dialog due to a Qt bug. (#8143)

Trying to use qutebrowser after it’s been deleted/moved on disk (e.g. after a Python upgrade) should now not crash anymore.

When the QtWebEngine resources dir couldn’t be found, qutebrowser now doesn’t crash anymore (but QtWebEngine still might).

Fixed a rare crash in the completion widget when there was no selection model when we went to clear that, probably when leaving a mode. (#7901)

Worked around a minor issue around QTimers on Windows where the IPC server could close the socket early. (#8191)

The latest PDF.js release (v4.2.67) is now supported when backed by QtWebEngine 6.6+ (#8170)

The darkmode settings grayscale.all, grayscale.images and increase_text_contrast got removed, following removals in Chromium.

New smart-simple value for colors.webpage.darkmode.policy.images, which on QtWebEngine 6.6+ uses a simpler classification algorithm to decide whether to invert images.

New content.javascript.legacy_touch_events setting, with those now being disabled by default, following a Chromium change.

Upgraded the bundled Qt version to 6.6.1, based on Chromium 112. Note this is only relevant for the macOS/Windows releases, on Linux those will be upgraded via your distribution packages.

Upgraded the bundled Python version for macOS/Windows to 3.12

The colors.webpage.darkmode.threshold.text setting got renamed to colors.webpage.darkmode.threshold.foreground, following a rename in Chromium.

With Qt 6.6, the content.canvas_reading setting now works without a restart and supports URL patterns.

Some web pages jumping to the top when the statusbar is hidden or (with v3.0.x) when a prompt is hidden.

Compatibility with PDF.js v4

Added an elaborate workaround for a bug in QtWebEngine 6.6.0 causing crashes on Google Mail/Meet/Chat, and a bug in QtWebEngine 6.5.0/.1/.2 causing crashes there with dark mode.

Made a rare crash in QtWebEngine when starting/retrying a download less likely to happen.

Graphical glitches in Google sheets and PDF.js, again. Removed the version restriction for the default application of qt.workarounds.disable_accelerated_2d_canvas as the issue was still evident on Qt 6.6.0. (#7489)

The colors.webpage.darkmode.threshold.foreground setting (.text in older versions) now works correctly with Qt 6.4+.

Upgraded the bundled Qt version to 6.5.3. Note this is only relevant for the macOS/Windows releases, on Linux those will be upgraded via your distribution packages. This Qt patch release comes with various important fixes, among them:

The "restore video" functionality of the view_in_mpv script works again on webengine.

Setting url.auto_search to dns works correctly now with Qt 6.

Counts passed via keypresses now have a digit limit (4300) to avoid exceptions due to cats sleeping on numpads. (#7834)

Navigating via hints to a remote URL from a file:// one works again. (#7847)

The timers related to the tab audible indicator and the auto follow timeout no longer accumulate connections over time. (#7888)

The workaround for crashes when using drag & drop on Wayland with Qt 6.5.2 now also works correctly when using wayland-egl rather than wayland as Qt platform.

Worked around a weird TypeError with QProxyStyle / TabBarStyle on certain platforms with Python 3.12.

Removed 1px border for the downloads view, mostly noticeable when it’s transparent.

Due to a Qt bug, cloning/undoing a tab which was not fully loaded caused qutebrowser to crash. This is now fixed via a workaround.

Graphical glitches in Google sheets and PDF.js via a new setting qt.workarounds.disable_accelerated_2d_canvas to disable the accelerated 2D canvas feature which defaults to enabled on affected Qt versions. (#7489)

The download dialog should no longer freeze when browsing to directories with many files. (#7925)

The app.slack.com User-Agent quirk now targets chromium 112 on Qt versions lower than 6.6.0 (previously it always targets chromium 99) (#7951)

Workaround a Qt issue causing jpeg files to not show up in the upload file picker when it was filtering for image filetypes (#7866)

qutebrowser now supports Qt 6 and uses it by default. Qt 5.15 is used as a fallback if Qt 6 is unavailable. This behavior can be customized in three ways (in order of precedence):

Various commands were renamed to better group related commands:

Releases are now automated on CI, and GPG signed by qutebrowser bot <bot@qutebrowser.org>, fingerprint 27F3 BB4F C217 EECB 8585 78AE EF7E E4D0 3969 0B7B. The key is available as follows:

Support for old Qt versions (< 5.15), old Python versions (< 3.8) and old macOS (< 11)/Windows (< 10) versions were dropped. See the "Removed" section below for details.

On invalid commands/settings with a similarly spelled match, qutebrowser now suggests the correct name in its error messages.

New :prompt-fileselect-external command which can be used to spawn an external file selector (fileselect.folder.command) from download filename prompts (bound to <Alt+e> by default).

New qute://start built-in start page (not set as the default start page yet).

New content.javascript.log_message.levels setting, allowing to surface JS log messages as qutebrowser messages (rather than only logging them). By default, errors in internal qute: pages and userscripts are shown to the user.

New content.javascript.log_message.excludes setting, which allows to exclude certain messages from the content.javascript.log_message.levels setting described above.

New tabs.title.elide setting to configure where text should be elided (replaced by …) in tab titles when space runs out.

New --quiet switch for :back and :forward, to suppress the error message about already being at beginning/end of history.

New qute-1pass userscript using the 1password commandline to fill passwords.

On macOS when running with Qt < 6.3, pyobjc-core and pyobjc-framework-Cocoa are now required dependencies. They are not required on other systems or when running with Qt 6.3+, but still listed in the requirements.txt because it’s impossible to tell the two cases apart there.

New features in userscripts:

New qt.chromium.experimental_web_platform_features setting, which is enabled on Qt 5 by default, to maximize compatibility with websites despite an aging Chromium backend.

New colors.webpage.darkmode.increase_text_contrast setting for Qt 6.3+

New fonts.tooltip, colors.tooltip.bg and colors.tooltip.fg settings.

New log-qt-events debug flag for -D

New --all flags for :bookmark-del and :quickmark-del to delete all quickmarks/bookmarks.

Python 3.8.0 or newer is now required.

Support for Python 3.6 and 3.7 is dropped, as they both reached their end of life in December 2021 and June 2023, respectively.

Support for Qt/PyQt before 5.15.0 and QtWebEngine before 5.15.2 are now dropped, as older Qt versions are end-of-life upstream since mid/late 2020 (5.13/5.14) and late 2021 (5.12 LTS).

The --enable-webengine-inspector flag is now dropped. It used to be ignored but still accepted, to allow doing a :restart from versions older than v2.0.0. Thus, switching from v1.x.x directly to v3.0.0 via :restart will not be possible.

Support for macOS 10.14 and 10.15 is now dropped, raising the minimum required macOS version to macOS 11 Big Sur.

Support for Windows 8 and for Windows 10 before 1607 is now dropped.

Support for 32-bit Windows is now dropped.

The qutebrowser icons got moved from icons/ to qutebrowser/icons in the repository, so that it’s possible for qutebrowser to load them using Python’s resource system (rather than compiling them into a Qt resource file). Packagers are advised to use misc/Makefile if possible, which has been updated with the new paths.

The content.javascript.can_access_clipboard setting got renamed to content.javascript.clipboard and now understands three different values rather than being a boolean: none (formerly false), access (formerly true) and access-paste (additionally allows pasting content, needed for websites like Photopea or GitHub Codespaces).

The default hints.selectors now also match the treeitem ARIA roles.

The :click-element command now can also click elements based on its ID (id), a CSS selector (css), a position (position), or click the currently focused element (focused).

The :click-element command now can select the first found element via --select-first.

New search.wrap_messages setting, making it possible to disable search wrapping messages.

The :session-save command now has a new --no-history flag, to exclude tab history.

New widgets for statusbar.widgets:

Messages shown by qutebrowser now don’t automatically get interpreted as rich text anymore. Thus, e.g. :message-info <h1>test now shows the given text. To show rich text with :message-* commands, use their new --rich flag. Note this is NOT a security issue, as only a small subset of HTML is interpreted as rich text by Qt, independently from the website.

Improved output when loading Greasemonkey scripts.

The macOS .app now is registered as a handler for .mhtml files, such as the ones produced by :download --mhtml.

The "… called unimplemented GM_…" messages are now logged as info JS messages instead of errors.

For QtNetwork downloads (e.g. :adblock-update), various changes were done for how redirects work:

Insecure redirects (HTTPS → HTTP) now fail the download.

20 redirects are now allowed before the download fails rather than only 10.

A redirect to the same URL will now fail the download with too many redirects instead of being ignored.

When a download fails in a way it’d leave an empty file around, the empty file is now deleted.

With Qt 6, setting content.headers.referer to always will act as if it was set to same-domain. The documentation is now updated to point that out.

With QtWebEngine 5.15.5+, the load finished workaround was dropped, which should make certain operations happen when the page has started loading rather when it fully finished.

mkvenv.py has a new --pyqt-snapshot flag, allowing to install certain packages from the Riverbank development snapshots server.

When QUTE_QTWEBENGINE_VERSION_OVERRIDE is set, it now always wins, no matter how the version would otherwise have been determined. Note setting this value can break things (if set to a wrong value), and usually isn’t needed.

When qutebrowser is run with an older QtWebEngine version as on the previous launch, it now prints an error before starting (which causes the underlying Chromium to remove all browsing data such as cookies).

The keys "<To Do List>" and "<Contrast adjust>" are now named "<To-do list>" and "<Adjust contrast>", respectively.

The tox.ini now requires at least tox 3.20 (was tox 3.15 previously).

:config-diff now has an --include-hidden flag, which also shows internally-set settings.

Improved error messages when :spawn can’t find an executable.

When a process fails, the error message now suggests using :process PID with the correct PID (rather than always showing the latest process, which might not be the failing one)

When a process got killed with SIGTERM, no error message is now displayed anymore (unless started with :spawn --verbose).

When a process got killed by a signal, the signal name is now displayed in the message.

The js-string-replaceall quirk is now removed from the default content.site_specific_quirks.skip, so that String.replaceAll is now polyfilled on QtWebEngine < 5.15.3, hopefully improving website compaitibility.

Hints are now displayed for elements setting an aria-haspopup attribute.

qutebrowser now uses SPDX license identifiers in its files. Full support for the REUSE specification (license provided in a machine-readable way for every single file) is not done yet, but planned for a future release.

When the devtools are clicked but input.insert_mode.auto_enter is set to false, insert mode now isn’t entered anymore.

The search wrapping messages are now correctly displayed in (hopefully) all cases with QtWebEngine.

When a message with the same text as a currently already displayed one gets shown, qutebrowser used to only show one message. This is now only done when the two messages are completely equivalent (text, level, etc.) instead of doing so when only the text matches.

The progress and backforward statusbar widgets now stay removed if you choose to remove them. Previously they would appear again on navigation.

Rare crash when running userscripts with crashed renderer processes.

Multiple rare crashes when quitting qutebrowser.

The asciidoc2html.py script now correctly uses the virtualenv-installed asciidoc rather than requiring a system-wide installation.

"Package would be ignored" deprecation warnings when running setup.py.

ResourceWarning when using :restart.

Crash when shutting down before fully initialized.

Crash with some notification servers when the server is quitting.

Crash when using QtWebKit with PAC and the file has an invalid encoding.

Crash with the "tiramisu" notification server.

Crash when the "herbe" notification presenter doesn’t start correctly.

Crash when no notification server is installed/available.

Warning with recent versions of the "deadd" (aka "linux notification center") notification server.

Crash when using :print --pdf with a directory where its parent directory did not exist.

The PyQt{5,6}.sip version is now shown correctly in the :version/--version output. Previously that showed the version from the standalone sip module which was only set for PyQt5. (#7805)

When a config.py calls .redirect() via a request interceptor (which is unsupported) and supplies an invalid redirect target URL, an exception is now raised for the .redirect() call instead of later inside qutebrowser.

Crash when loading invalid history items from a session file.

Support SQLite with DQS (double quoted string) compile time option turned off.

New array_at quirk, polyfilling the Array.at method, which is needed by various websites, but only natively available with Qt 6.2.

Crash when the adblock filter file can’t be read.

Inconsistent behavior when using :config-{dict,list}-* commands with an invalid value. Before the fix, using the same command again would complain that the value was already present, despite the error and the value not being actually changed.

Incomplete error handling when mutating a dict/list in config.py and setting an invalid value. Before the fix, this would result in either a message in the terminal rather than GUI (startup), or in a crash (:config-source).

Wrong type handling when using :config-{dict,list}-* commands with a config option with non-string values. The only affected option is bindings.commands, which is probably rarely used with those commands.

The readability userscript now correctly passes the source URL to Breadability, to make relative links work.

Update dictcli.py to use the main branch, fixing a 404 error.

Crash with some notification servers when the server did quit.

Minor documentation fixes

Packaging-related fixes:

The notification fixes in v2.5.1 caused new notification crashes (probably more common than the ones being fixed…). Those are now fixed, along with a (rather involved) test case to prevent similar issues in the future.

When a text was not found on a page, the associated message would be shown as rich text (e.g. after /<h1>). With this release, this is fixed for search messages, while the 3.0.0 release will change the default for all messages to be plain-text. Note this is NOT a security issue, as only a small subset of HTML is interpreted as rich text by Qt, independently from the website.

When a Greasemonkey script couldn’t be loaded (e.g. due to an unreadable file), qutebrowser would crash. It now shows an error instead.

Ever since the v1.2.0 release in 2018, the content.default_encoding setting was not applied on start properly (only when it was changed afterwards). This is now fixed.

The qute-pass userscript is marked as executable again.

PDF.js now works properly again with the macOS and Windows releases.

The MathML workaround for darkmode (e.g. black on black Wikipedia formula) now also works for display (rather than inline) math.

The content.proxy setting can now correctly be set to arbitrary values via the qute://settings page again.

Fixed issues with Chromium version detection on Archlinux with qt5-webengine 5.15.9-3.

Fixed a rare possible crash with invalid Content-Disposition headers.

Fixes for various notification-related crashes:

Fixes in userscripts:

v2.5.x will be the last release of qutebrowser 2. For the upcoming 3.0.0 release, it’s planned to drop support for various legacy platforms and libraries which are unsupported upstream, such as:

The :rl-unix-word-rubout command (<Ctrl-W> in command/prompt modes) has been deprecated. Use :rl-rubout " " instead.

The :rl-unix-filename-rubout command has been deprecated. Use either :rl-rubout "/ " (classic readline behavior) or :rl-filename-rubout (using OS path separator and ignoring spaces) instead.

Improved message if a spawned process wasn’t found and a Flatpak container is in use.

The :tab-move command now takes start and end as index to move a tab to the first/last position.

Tests now automatically pick the backend (QtWebKit/QtWebEngine) based on what’s available. The QUTE_BDD_WEBENGINE environment variable and --qute-bdd-webengine argument got replaced by QUTE_TESTS_BACKEND and --qute-backend respectively, which can be set to either webengine or webkit.

Using :tab-give or :tab-take on the last tab in a window now always closes that window, no matter what tabs.last_close is set to.

Redesigned qute://settings (:set) page with buttons for options with fixed values.

The default hint.selectors now match more ARIA roles (tab, checkbox, menuitem, menuitemcheckbox and menuitemradio).

Using e.g. :bind --mode=passthrough now scrolls to the passthrough section on the qute://bindings page.

Clicking on a notification now tries to focus the tab where the notification is coming from. Note this might not work properly if there is more than one tab from the same host open.

Improvements to userscripts:

The content.headers.custom setting now accepts empty strings as values, resulting in an empty header being sent.

Renamed settings:

System-wide userscripts are now discovered from the correct location when running via Flatpak (/app/share rather than /usr/share).

Filename prompts now don’t display a .. entry in the list of files anymore. To get back to the parent directory, either type ../ manually, or use the new :rl-filename-rubout command, bound to <Ctrl-Shift-W> by default.

New input.match_counts option which allows to turn off count matching for more emacs-like bindings.

New {relative_index} field for tabs.title.format (and .pinned_format) which shows relative tab numbers.

New input.mode_override option which allows overriding the current mode based on the new URL when navigating or switching tabs.

New qt.chromium.sandboxing setting which allows to disable Chromium’s sandboxing (mainly intended for development and testing).

New QUTE_TAB_INDEX variable for userscripts, containing the index of the current tab.

New editor.remove_file setting which can be set to False to keep all temporary editor files after closing the external editor.

New :rl-rubout command replacing :rl-unix-word-rubout (and optionally :rl-unix-filename-rubout), taking a delimiter as argument.

New :rl-filename-rubout command, using the OS path separator and ignoring spaces. The command also gets shown in the suggested commands for a download filename prompt now.

When search.incremental is disabled, searching using /text followed by a backwards search via ?text (or vice-versa) now correctly changes the search direction.

Elements getting a hint due to a tabindex now are skipped if it’s set to -1, reducing some false-positives.

The audible indicator ([A]) now uses a 2s cooldown when the audio goes silent, equivalent with the behavior of older QtWebEngine versions.

With confirm_quit set to downloads, the confirmation dialog is now only shown when closing the last window (rather than closing any window, which would continue running that window’s downloads). Unfortunately, more issues with confirm_quit and multiple windows remain.

Crash when a previous crash-log file contains non-ASCII characters (which should never happen unless it was edited manually)

Due to changes in Debian, an old workaround (for broken QtWebEngine patching on Debian) caused the inferior qutebrowser error page to be displayed, when Chromium’s would have worked fine. The workaround was now dropped.

Crash when using <Ctrl-D> (:completion-item-del) in the :tab-focus list, rather than :tab-select.

Work around a Qt issue causing :spawn to run executables from the current directory if no system-wide executable was found. The underlying Qt bug is tracked as CVE-2022-25255, though the impact with typical qutebrowser usage is low: Normally, qutebrowser is run from a fixed location (usually the users home directory), and :spawn is not typically used with executables that don’t exist. The main security impact of this bug is in tools like text editors, which are often executed in untrusted directories and might attempt to run auxiliary tools automatically.

When :rl-rubout or :rl-filename-rubout (formerly :rl-unix-word-rubout and :rl-unix-filename-rubout) were used on a string not starting with the given delimiter, they failed to delete the first character, which is now fixed.

Fixes in userscripts:

Speculative fix for an immediate crash at start with the macOS/Windows binaries (in certain rare environments).

Speculative fix for a qutebrowser crash when the notification daemon crashes while showing the notification.

Fix crash when using :screenshot with an invalid --rect argument.

Added a site-specific quirk to make cookie dialogs on StackExchange pages (such as Stack Overflow) work on Qt 5.12.

CVE-2021-41146: Fix arbitrary command execution on Windows via URL handler argument injection. See the security advisory for details.

New content.blocking.hosts.block_subdomains setting which can be used to disable the subdomain blocking for the hosts-based adblocker introduced in v2.3.0.

New downloads.prevent_mixed_content setting to prevent insecure mixed-content downloads (true by default).

New --private flag for :tab-clone, which clones a tab into a new private window, mirroring the same flags for :open and :tab-give.

Switching tabs via mouse wheel scrolling now works properly on macOS. Set tabs.mousewheel_switching to false if you prefer the previous behavior.

Speculative fix for a crash when closing qutebrowser while a systray notification is shown.

Typing in the filename prompt now filters matching directories.

When opening a file qutebrowser can’t handle from a file:/// directory listing, qutebrowser now opens it with the default application rather than displaying a download prompt.

In Greasemonkey scripts, using "overrideMimeType" with GM_xmlhttpRequest is now supported.

:hint --rapid is now supported for the tab hinting target no matter what tabs.background is set to, as there are various scenarios where tabs can open in the background.

New flags for the qute-pass userscript:

In insert mode, <Shift-Escape> is now bound to fake-key <Escape> by default, i.e., sends an Escape keypress to the website.

Using GM_setClipboard in Greasemonkey scripts is now supported.

Updated the workaround for Google Account log in claiming that this browser isn’t secure. For an equivalent workaround on older versions, run: :set -u https://accounts.google.com/* content.headers.user_agent "Mozilla/5.0 ({os_info}; rv:90.0) Gecko/20100101 Firefox/90.0"

Corrupt cache file exceptions with adblock 0.5.0+ are now handled properly.

Crash when entering unicode surrogates into the filename prompt.

UnboundLocalError in qute-keepass when the database couldn’t be opened.

New content.prefers_reduced_motion setting to request websites to reduce non-essential motion/animations.

New colors.prompts.selected.fg setting to customize the text color for selected items in filename prompts.

The hosts-based adblocker (using content.blocking.hosts.lists) now also blocks all requests to any subdomains of blocked hosts.

The fonts.web.* settings now support URL patterns.

The :greasemonkey-reload command now shows a list of loaded scripts and has a new --quiet switch to suppress that message.

When launching a userscript via hints, a new QUTE_CURRENT_URL environment variable now points to the current page (rather than the URL of the selected element, where QUTE_URL points to).

Crash on macOS 10.14+ when logging into Google accounts — the previous fix was incomplete due wrong information in Apple’s documentation.

Crash when two Greasemonkey scripts have the same name (usually happening because the same file is in both the data and the config directory).

Deprecation warnings when using the link_pyqt.py script on Python 3.10 (e.g. via tox or mkvenv.py).

Logging into Google accounts or sharing the camera on macOS 10.14+ crashed, which is now fixed.

The Windows installer now correctly aborts the installation on Windows 7 (rather than attempting an install which won’t work, since Windows 7 is unsupported since the v2.0.0 release).

Using --json-logging without --debug caused qutebrowser to crash since the v1.13.0 release. It now works correctly again.

Mixing Qt 5.14+ with QtWebEngine 5.12 caused a crash related to qutebrowser’s notification support, which is now fixed.

The documentation now points to the new IRC channels on irc.libera.chat instead of the defunct Freenode channels (due to a hostile takeover by Freenode staff).

Setting content.headers.user_agent or .accept_language to a value containing non-ascii characters was permitted by qutebrowser, but resulted in a crash when loading a page. Such values are now rejected properly.

When quitting qutebrowser on the qute://settings page, a crash could happen, which is now fixed.

When :edit-text is used, but the existing text in the input isn’t representable in the configured encoding (editor.encoding), qutebrowser would crash. It now shows a proper error instead.

The testsuite should now work properly on aarch64.

When QtWebEngine is in a "stuck" state while :selection-follow was used, this could cause a crash in qutebrowser. This is now fixed (speculatively, due to lack of a reproducer).

When the brave adblock data (adblock-cache.dat) got corrupted, qutebrowser would crash when trying to load it. It now displays an error instead.

Combining /S (silent) and /allusers when uninstalling via the Windows installer now works properly.

When awesomewm’s "naughty" notification daemon was used with a development version of AwesomeWM and an unknown version number, qutebrowser would crash when trying to parse the version string. This is now fixed.

Due to a bug with QtWebEngine 5.15.4, old Service Worker data could cause renderer process crashes. This is now worked around by qutebrowser.

When an (broken) binding to set-cmd-text without any argument existed, using : would crash, which is now fixed.

New site-specific quirk (again) working around not being able to type accented/composed characters on Google Docs.

When running with python -OO (which is not recommended), a notification being shown would result in a crash, which is now fixed.

When an error occurs in a notification presenter, qutebrowser now shows that error in the statusbar instead of just logging it.

New site-specific-quirk for Discord logging users out when using vertical tabs (yes, really)

Certain errors from notification daemons are now displayed as non-fatal errors instead of qutebrowser crashing:

The mkvenv.py script now works when ldconfig -p is failing.

Running :spawn -u -o broke in v2.2.0 and now works properly again.

Fixes in userscripts:

Running qutebrowser with Qt 5.12.0 is now unsupported and logs a warning. It should still work - however, a workaround for issues with the Nvidia graphic driver was dropped. Newer Qt 5.12.x versions are still fully supported.

The --force argument for :tab-only is deprecated, use --pinned close instead.

Using :tab-focus without an argument or count is now deprecated, use :tab-next instead.

New dependency on the QtDBus module. If this requirement is an issue for you or your distribution, please open an issue! Note that a DBus connection at runtime is still optional.

New input.media_keys setting which can be used to disable Chromium’s handling of media keys.

New :process command (and associated qute://process pages) which can be used to view and terminate/kill external processes spawned by qutebrowser.

New content.site_specific_quirks.skip setting which can be used to disable individual site-specific quirks.

New --pinned argument for :tab-only, which replaces --force (with --pinned close), but also can take --pinned keep to keep pinned tabs without prompting.

New fileselect.folder.command which can be used with fileselect.handler = external to customize the command to use to upload directories (<input type="file" webkitdirectory /> elements, which are non-standard but in wide use).

New content.notifications.presenter setting with various new ways to show web notifications:

New content.notifications.show_origin setting, which can be used to decide for which notifications to show the origin (the URL the notification was sent from).

The content.ssl_strict setting got renamed to content.tls.certificate_errors, with new values:

The new content.tls.certificate_errors setting now also understands the value ask-block-thirdparty, which asks for page loads but automatically blocks resource loads on TLS errors. This behavior is consistent with what other browsers do.

The prompt text shown on certificate errors has been improved to make it clearer what kind of error occurred exactly.

The content.site_specific_quirks setting got renamed to content.site_specific_quirks.enabled.

The content.notifications option got renamed to content.notifications.enabled.

The completion now also shows bindings starting with set-cmd-text in its third column, such as o for :open.

When :spawn is used with the -m / --output-messages flag, the output now appears live, while the process is running.

When a shown message replaces an existing related one (e.g. for zoom levels), the replacing now also works even if a different message was shown in between.

The .redirect(...) method on interceptors now supports an ignore_unsupported=True argument which suppresses exceptions if a request could not be redirected. Note, however, that it is still not public API.

When the --config-py argument is used, no warning about a missing config.load_autoconfig is shown anymore, as the argument is typically used for temporarily testing a config.

The internal _autosave session used for crash recovery is now only saved once per minute, since saving it for every page load is a noticeable performance issue.

The readability-js userscript now displays a small header with page information.

When an external file selector is used, some additional validation is done on the picked files now, so that errors are shown if e.g. a directory is selected when a file was expected.

The default binding for T (:tab-focus) got changed so that it fills the command line with :tab-focus if used without a count (instead of being equivalent to :tab-next in that case).

The :config-unset command now understands the --pattern (-u) flag to unset options customized for a given URL pattern (such as after answering a prompt with "always"/"never").

The :config-unset command now shows an error when used on an option which is valid, but was never customized.

The statusbar.widgets setting now understands text:... entries which allows adding a hard-coded text to the statusbar.

The polyfill for String.replaceAll (required for Nextcloud Calendar < 2.2.0 with QtWebEngine < 5.15.3) is now disabled by default, as it’s not fully compliant to the ECMAScript spec and might cause issues on other websites. If you still need it (e.g. if you’re still on an old Nextcloud Calendar version), remove js-string-replaceall from content.site_specific_quirks.skip.

When an editor exits with a != 0 exit status, the temporary editor file is now persisted. This already was the case when the editor crashed.

When a nonexistent file gets passed to --config-py, qutebrowser now complains instead of silently not loading it.

With some (rare) setups, opening the report dialog or using a PAC proxy with QtWebKit could result in qutebrowser hanging due to a PyQt bug. There’s now a workaround which prevents the hang.

QtWebEngine version detection (influencing things like dark mode settings or certain workarounds) now works correctly on OpenBSD.

Certain version number formats in /etc/os-release caused qutebrowser to crash. Those are now handled correctly.

The macOS releases now properly support Dark Mode for UI elements by setting NSRequiresAquaSystemAppearance to false.

The qute://spawn-output page used by :spawn -o is now removed, as it’s replaced by the new qute://process pages.

Site-specific quirk for krunker.io, which shows a "Socket Error" with qutebrowser’s default Accept-Language header. The workaround is equivalent to doing :set -u matchmaker.krunker.io content.headers.accept_language "".

Clicking the x in the devtools window to hide it now also leaves insert mode.

The workaround for black on (almost) black formula images in dark mode now also works with Qt 5.12 and 5.13.

When running in Flatpak or with the Windows/macOS releases, the QtWebEngine version is now detected properly. Before, a wrong version was assumed, breaking dark mode and certain workarounds (resulting in crashes on websites like LinkedIn or TradingView).

When the metainfo in the completion database doesn’t have the expected structure, qutebrowser now tries to gracefully recover from the situation instead of crashing.

When qutebrowser displays an error during initialization, opening a second instance would lead to a crash. Instead, qutebrowser now ignores the attempt to open a new page as long as it’s not fully initialized yet.

When the Brave adblock cache folder was unreadable, qutebrowser crashed. It now displays an error instead.

Fixes in the qute-pass userscript for gopass:

When using bindings.key_mappings to map a key to multiple other keys, qutebrowser would crash. This is now handled correctly - however, note that it’s usually better to map keys to commands instead.

When a minimized window is selected via :tab-select, it’s now un-minimized properly.

When a format string in the config (e.g. tabs.title_format) used a value like {current_url.host} (instead of {current_url:host}), qutebrowser would crash. It now correctly reports an invalid config value instead.

In rare circumstances, sending URLs/commands to existing instances would result in a crash, which is now fixed.

Running the testsuite should now fully work without internet access again.

The --asciidoc script for mkvenv.py broke with v1.14.0. It now works correctly again.

Various other fixes for running in Flatpak (backported in the Flatpak release even before this qutebrowser release).

We are the Knights Who Say… :Ni!

The following command aliases were deprecated in v2.0.0 and are now removed:

New :screenshot command which can be used to screenshot the visible part of the page.

New optional dependency on the importlib_metadata project on Python 3.7 and below. This is only relevant when PyQtWebEngine is installed via pip - thus, this dependency usually isn’t relevant for packagers.

New qute-keepassxc userscript integrating with the KeePassXC browser API.

Initial support for QtWebEngine 5.15.3 and PyQt 5.15.3/.4

The colors.webpage.prefers_color_scheme_dark setting got renamed to colors.webpage.preferred_color_scheme and now takes the values auto, light and dark (instead of being True for dark and False for auto). Note that the light value is only supported with Qt 5.15.2+, falling back to the same behavior as auto on older versions.

On Linux, qutebrowser now tries harder to find details about the installed QtWebEngine version by inspecting the QtWebEngine binary. This should reduce issues with dark mode (and some workarounds) not working when using differing versions of QtWebEngine/PyQtWebEngine/Qt. This change also prepares qutebrowser for QtWebEngine 5.15.3, which will get released without an updated Qt.

When PyQtWebEngine >= 5.15.3 is installed via pip (as is e.g. the case with mkvenv.py), qutebrowser now queries the associated metadata to find out the QtWebEngine version.

When doing :hint links yank --rapid, the messages shown now replace each other, thus being less noisy.

Newlines in JavaScript messages (confirm, prompt and alert) are now preserved.

Messages in prompts are now word-wrapped rather than displaying them in one long line.

If a command stats with space (e.g. : open ..., it’s now not saved to command history anymore (similar to how some shells work).

When a tab is pinned, running :open will now open a new tab instead of displaying an error.

The fileselect.*.command settings now support file selectors writing the selected paths to stdout, which is used if no {} placeholder is contained in the configured command.

The --debug-flag argument now understands a new log-sensitive-keys value which logs all keypresses (including those in insert/passthrough/prompt/… mode) for debugging.

The readability and readability-js userscripts now add a qute-readability CSS class to the page, so that it can be styled easily via a user stylesheet.

With QtWebEngine 5.15.3 and some locales, Chromium can’t start its subprocesses. As a result, qutebrowser only shows a blank page and logs "Network service crashed, restarting service.". This release adds a qt.workarounds.locale setting working around the issue. It is disabled by default since distributions shipping 5.15.3 will probably have a proper patch for it backported very soon.

The colors.webpage.preferred_color_scheme and colors.webpage.darkmode.* settings now work correctly with QtWebEngine 5.15.3 (and Gentoo, which at the time of writing packages 5.15.3 disguised as 5.15.2).

When dark mode settings were set, existing blink-features arguments in qt.args (or --qt-flag) were overridden. They are now combined properly.

On QtWebEngine 5.15.2, auto detection for the prefers-color-scheme media query is broken and always returns no-preference, which was removed from the CSS WG Specification. This release contains a workaround to always return light instead (as per the spec).

When an external file selector deletes the temporary file (like nnn does when quitting the terminal), qutebrowser would crash. It now displays an error instead. The same applies if the temporary file is unreadable for any other reason.

On macOS, a change in v2.0.x caused certain shortcuts to not work with Cmd anymore, using Ctrl instead. They now work correctly using Cmd (like usual on macOS) again.

On macOS, using F (hint all tab) sometimes would open a context menu instead of following a link. This is now fixed.

The quirk added for a missing String.replaceAll did not handle special regexp characters correctly, thus breaking some sites. It now handles them properly.

The "try again" button on error pages now works correctly with JavaScript disabled.

If a GreaseMonkey script doesn’t have a "@run-at" comment, qutebrowser accidentally treated that as "@run-at document-idle". However, other GreaseMonkey implementations default to "@run-at document-end" instead, which is what qutebrowser now does, too.

The hist_importer.py script didn’t work correctly after qutebrowser v2.0.0 and resulted in a history database qutebrowser couldn’t read properly. It now works properly again.

With certain QtWebEngine versions (5.15.0 based on Chromium 80 and 5.15.3 based on Chromium 87), Chromium’s dark mode doesn’t invert certain SVG images, even with colors.wegpage.darkmode.policy.images set to smart. Most notably, this causes formulae on Wikipedia to display black on (almost) black. If content.site_specific_quirks is enabled, qutebrowser now injects some CSS as a workaround, which inverts all math formula images on Wikipedia (and potentially other sites, if they use the same CSS class).

When a hint label text started with an apostrophe, it would show an escaped text until the hints first character has been pressed. It now shows up correctly.

When right-clicking an empty part of the downloads bar, qutebrowser v2.0.x would crash. This is now fixed.

Setting content.cookies.store to false only worked properly when this was done after qutebrowser was already started due to a regression in v2.0.0. It now works as expected again.

If qutebrowser was installed as a Python egg with Python 3.8 or 3.9, requesting unavailable resource files (such as PDF.js not being bundled, or a missing changelog file) caused in a crash due to an inconsistent behavior in those versions of Python. This is now handled properly by qutebrowser.

In v2.0.0, support for importing the sip dependency as sip rather than PyQt5.sip was dropped, since upstream claims it should be used as PyQt5.sip ever since PyQt 5.11. However, some distributions still package sip as a global sip package. Thus, support for a global sip package is now reintroduced.

The changelog for v2.0.0 claimed that hints.leave_on_load was set to true by default. However, the input.insert_mode.leave_on_load setting was instead set to true accidentally. This is now fixed by actually setting hints.leave_on_load to true, and reversing the change to input.insert_mode.leave_on_load so it is set to false by default again.

When the importlib_resources package is required but was missing, users would get a Python stacktrace rather than a proper error message. This is now fixed.

Site-specific quirk JavaScript files were loaded lazily rather than preloaded at the start of qutebrowser, causing a crash when e.g. switching between versions while qutebrowser is open. Now they are preloaded at the start of qutebrowser again.

The link to the keybinding cheatsheet on the internal :help page wasn’t displayed correctly. This is now fixed.

When the completion rebuilding process was interrupted, qutebrowser did not detect this condition on the next start, thus resulting in a completion with inconsistent data. This is now fixed, with another rebuild being forced with this update, to ensure the data is consistent for all users.

In certain scenarios, qutebrowser v2.0.x warned about config.load_autoconfig(...) being missing when loading a secondary config (e.g. via config.source(...)). It now only shows those warnings for the main config.py file.

The --enable-webengine-inspector flag is now accepted again, however it’s unused and undocumented. It purely exists to make it possible to use :restart between pre-v2.0.x and v2.0.2+ versions.

When hints.dictionary pointed to a file not encoded as UTF-8, this resulted in a crash (also in versions before v2.0.0). It now properly displays an error instead.

When running qutebrowser with a single empty commandline argument, such as done by open_url_in_instance.sh, this would result in a partially initialized window. Interacting with that window results in a crash (also in versions before v2.0.0). Instead, the startpage is now shown properly.

If qutebrowser was installed as a Python egg (similar to a .zip file, via setup.py install under certain conditions), a change in v2.0.0 caused it to not start properly. This is now fixed.

If qutebrowser was set up (or packaged) in an unclean environment, this could result in a stale qutebrowser/components/adblock.py file being picked up. That file is not part of the release anymore, but if an old version is still around, causes qutebrowser to crash. It’s now explicitly blocked inside qutebrowser so it gets ignored even if it still exists.

When the adblocking method was switched using :set, and the adblock dependency was unavailable when qutebrowser started (but was installed while qutebrowser was open), this resulted in a crash. Now a warning prompting for a restart of qutebrowser is shown instead.

The format_json userscript now uses sh instead of bash again.

The add-nextcloud-bookmarks, add-nextcloud-cookbook, readability and ripbang userscripts now use a python3 rather than plain python shebang.

When QTWEBENGINE_CHROMIUM_FLAGS is set in the environment, this causes flag handling (including workarounds for QtWebEngine crashes) inside qutebrowser to break. This will be handled properly in a future version, but this release now shows a warning on standard output if this is the case.

The config completion for fileselect.*.command now also includes the "nnn" terminal file manager.

If the Python adblock library is available, it is now used to integrate Brave’s Rust adblocker library for improved adblocking based on ABP-like filter lists (such as EasyList). If it is unavailable, qutebrowser falls back to host-blocking, i.e. the same blocking technique it used before this release. As part of this, various settings got renamed, see "Changed" below. Note: If the adblock dependency is available, qutebrowser will ignore custom host blocking via the blocked-hosts config file or file:/// URLs supplied as host blocking lists. You will need to either migrate those to ABP-like lists, or set content.blocking.method to both.

Various dependency upgrades - a quick checklist for packagers (see "Changed" below for details):

Dropped support for old OS versions in binary releases:

Various renamed settings and commands, see "Deprecated" and "Changed" below.

The --enable-webengine-inspector flag (which was only needed for Qt 5.10 and below) is now dropped. With Qt 5.11 and newer, the inspector/devtools are enabled unconditionally.

Support for moving qutebrowser data from versions before v1.0.0 has been removed.

The --old flag for :config-diff has been removed. It used to show customized options for the old pre-v1.0 config files (in order to aid migration to v1.0).

The :inspector command which was deprecated in v1.13.0 (in favor of :devtools) is now removed.

Several commands have been renamed for consistency and/or easier grouping of related commands. Their old names are still available, but deprecated and will be removed in qutebrowser v2.1.0.

New settings for the ABP-based adblocker:

New qt.environ setting which makes it easier to set/unset environment variables for qutebrowser.

New settings to use an external file picker (such as ranger or vifm):

When QtWebEngine has been updated but PyQtWebEngine hasn’t yet, the dark mode settings might stop working. As a (currently undocumented) escape hatch, this version adds a QUTE_DARKMODE_VARIANT=qt_515_2 environment variable which can be set to get the correct behavior in (transitive) situations like this.

New --desktop-file-name commandline argument, which can be used to customize the desktop filename passed to Qt (which is used to set the app_id on Wayland).

The :open completion now also completes local file paths and file:// URLs, via a new filesystem entry in completion.open_categories. Also, a new completion.favorite_paths setting was added which can be used to add paths to show when :open is used without any input.

New QUTE_VERSION variable for userscripts, which can be used to read qutebrowser’s version.

New "Copy URL" entry in the context menu for downloads.

New :bookmark-list command which lists all bookmarks/quickmarks. The corresponding qute://bookmarks URL already existed since v0.8.0, but it was never exposed as a command.

New qt.workarounds.remove_service_workers setting which can be used to remove the "Service Workers" directory on every start. Usage of this option is generally discouraged, except in situations where the underlying QtWebEngine bug is a known cause for crashes.

Changelogs are now shown after qutebrowser was upgraded. By default, the changelog is only shown after minor upgrades (feature releases) but not patch releases. This can be adjusted (or disabled entirely) via a new changelog_after_upgrade setting.

New userscripts:

config.py files now are required to have either config.load_autoconfig(False) (don’t load autoconfig.yml) or config.load_autoconfig() (do load autoconfig.yml) in them.

Various host-blocking settings have been renamed to accommodate the new ABP-like adblocker:

Changes to default settings:

On the first start, the history completion database is regenerated to remove a few problematic entries (such as long qute://pdfjs URLs). This might take a couple of minutes, but is a one-time operation. This should result in a performance improvement for the completion for affected users.

qutebrowser now shows an error if its history database version is newer than expected. This currently should never happen, but allows for potentially backwards-incompatible changes in future versions.

At least Python 3.6.1 is now required to run qutebrowser, support for Python 3.5 (and 3.6.0) is dropped. Note that Python 3.5 is no longer supported upstream since September 2020.

At least Qt/PyQt 5.12 is now required to run qutebrowser, support for 5.7 to 5.11 (inclusive) is dropped. While Debian Buster ships Qt 5.11, it’s based on a Chromium version from 2018 with no Debian security support and unsupported upstream since May 2019. It also has compatibility issues with various websites (GitHub, Twitch, Android Developer documentation, YouTube, …). Since no newer Debian Stable is released at the time of writing, it’s recommended to install qutebrowser in a virtualenv with a newer version of Qt/PyQt.

New optional dependency on the Python adblock library (see above for details).

The (formerly optional) cssutils dependency is now removed. It was only needed for improved behavior in corner cases when using :download --mhtml with the (non-default) QtWebKit backend, and as such it’s unlikely anyone is still relying on it. The cssutils project is also dead upstream, with its repository being gone after Bitbucket removed Mercurial support.

The (formerly required) pygments dependency is now optional. It is only used when using :view-source with QtWebKit, or when forcing it via :view-source --pygments on QtWebEngine. If it is unavailable, an unhighlighted fallback version of the page’s source is shown.

The former runtime dependency on the pkg_resources module (part of the setuptools project) got dropped. Note that setuptools is still required to run setup.py.

A new dependency on the importlib_resources module got introduced for Python versions up to and including 3.8. Note that the stdlib importlib.resources module for Python 3.7 and 3.8 is missing the needed APIs, thus requiring the backports for those versions as well.

The former dependency on the attrs/attr package is now dropped in favour of dataclasses in the Python standard library. On Python 3.6, a new dependency on the dataclasses backport is now required.

The former dependency on the pypeg2 package is now dropped. This might cause some changes for certain corner-cases for suggested filenames when downloading files with the QtWebKit backend.

Windows and macOS releases now ship Python 3.9 rather than 3.7.

The colors.webpage.darkmode.* settings are now also supported with older Qt versions (Qt 5.12 and 5.13) rather than just with Qt 5.14 and above.

For regexes in the config (hints.{prev,next}_regexes), certain patterns which will change meanings in future Python versions are now disallowed. This is the case for character sets starting with a literal [ or containing literal character sequences --, &&, ~~, or ||. To avoid a warning, remove the duplicate characters or escape them with a backslash.

If prompt(..., "default") is used via JS, the default text is now pre-selected in the prompt shown by qutebrowser.

URLs such as ::1/foo are now handled as a search term or local file rather than IPv6. Use [::1]/foo to force parsing as IPv6 instead.

The mkvenv.py script now runs a "smoke test" after setting up the virtual environment to ensure it’s working as expected. If necessary, the test can be skipped via a new --skip-smoke-test flag.

Both qutebrowser userscripts and Greasemonkey scripts are now additionally picked up from qutebrowser’s config directory (the userscripts and greasemonkey subdirectories of e.g. ~/.config/qutebrowser/) rather than only the data directory (the same subdirectories of e.g. ~/.local/share/qutebrowser/).

The :later command now understands a time specification like 5m or 1h5m2s, rather than just taking milliseconds.

The importer.py script doesn’t use a browser argument anymore; instead its --input-format switch can be used to configure the input format. The help also was expanded to explain how to use it properly.

If tabs.tabs_are_windows is set, the tabs.last_close setting is now ignored and the window is always closed when using :close (d).

With the (default) QtWebEngine backend, if a custom accept header is set via content.headers.custom, the custom value is now ignored for XHR (XMLHttpRequest) requests. Instead, the sent value is now */* or the header set from JavaScript, as it would be if content.headers.custom wasn’t set.

The :tab-select completion now shows the underlying renderer process PID if doing so is supported (on QtWebEngine 5.15).

If tabs.favicons.show is set to never, favicons aren’t unnecessarily downloaded anymore. Thus, disabling favicons can help with a possible fingerprinting vector.

"Super" is now understood as a modifier (i.e. as alias to "Meta").

Initial support for Python 3.10 (currently in Alpha stage).

Various performance improvements, including for the startup time.

With interpolated color settings (colors.tabs.indicator.* and colors.downloads.*), the alpha channel is now handled correctly.

Fixes to userscripts:

The :undo completion now sorts its entries correctly (by the numerical index rather than lexicographically).

The completion.web_history.ignore setting now works properly when set in config.py (rather than via :set). Additionally, a :config-source will not result in a history rebuild if the value wasn’t actually changed.

When downloading a data: URL, the suggested filename is now improved and contains a proper extension. Before this fix, qutebrowser would use the URL’s data contents as filename with QtWebEngine; or "binary blob" with the Qt network stack.

When :tab-only is run before a tab is available, an error is now shown instead of crashing.

A couple of long URLs (such as qute://pdfjs URLs) are now not added to the history database anymore.

A bug in QtWebEngine 5.15.2 causes "renderer process killed" errors on websites like LinkedIn and TradingView. There is now a workaround in qutebrowser to prevent this from happening.

Nextcloud Calendars started using String.replaceAll which was only added to Chromium recently (Chrome 85), so won’t work with current QtWebEngine versions. This release includes a workaround (a polyfill as a site-specific-quirk).

With v1.14.0, qutebrowser configures the main window to be transparent, so that it’s possible to configure a translucent tab- or statusbar. However, that change introduced various issues, such as performance degradation on some systems or breaking dmenu window embedding with its -w option. To avoid those issues for people who are not using transparency, the default behavior is reverted to versions before v1.14.0 in this release. A new window.transparent setting can be set to true to restore the behavior of v1.14.0.

Windows and macOS releases now ship Qt 5.15.2, which is based on Chromium 83.0.4103.122 with security fixes up to 86.0.4240.183. This includes CVE-2020-15999 in the bundled freetype library, which is known to be exploited in the wild. It also includes various other bugfixes/features compared to Qt 5.15.0 included in qutebrowser v1.14.0, such as:

Setting the content.headers.referer setting to same-domain (the default) was supposed to truncate referrers to only the host with QtWebEngine. Unfortunately, this functionality broke in Qt 5.14. It works properly again with this release, including a test so this won’t happen again.

With QtWebEngine 5.15, setting the content.headers.referer setting to never did still send referrers. This is now fixed as well.

In v1.14.0, a regression was introduced, causing a crash when qutebrowser was closed after opening a download with PDF.js. This is now fixed.

With Qt 5.12, the Object.fromEntries JavaScript API is unavailable (it was introduced in Chromium 73, while Qt 5.12 is based on 69). This caused https://www.vr.fi/en and possibly other websites to break when accessed with Qt 5.12. A suitable polyfill is now included with qutebrowser if content.site_specific_quirks is enabled (which is the default).

While XDG startup notifications (e.g. launch feedback via the bouncy cursor in KDE Plasma) were supported ever since Qt 5.1, qutebrowser’s desktop file accidentally declared that it wasn’t supported. This is now fixed.

The dmenu_qutebrowser and qutedmenu userscripts now correctly read the qutebrowser sqlite history which has been in use since v1.0.0.

With Python 3.8+ and vertical tabs, a deprecation warning for an implicit int conversion was shown. This is now fixed.

Ever since Qt 5.11, fetching more completion data when that data is loaded lazily (such as with history) and the last visible item is selected was broken. The exact reason is currently unknown, but this release adds a tentative fix.

When PgUp/PgDown were used to go beyond the last visible item, the above issue caused a crash, which is now also fixed.

As a workaround for an overzealous Microsoft Defender false-positive detecting a "trojan" in the (unprocessed) adblock list, :adblock-update now doesn’t cache the HTTP response anymore.

With the QtWebKit backend and content.headers set to same-domain (the default), origins with the same domain but different schemes or ports were treated as the same domain. They now are correctly treated as different domains.

When a URL path uses percent escapes (such as https://example.com/embedded%2Fpath), using :navigate up would treat the %2F as a path separator and replace any remaining percent escapes by their unescaped equivalents. Those are now handled correctly.

On macOS 11.0 (Big Sur), the default monospace font name caused a parsing error, thus resulting in broken styling for the completion, hints, and other UI components. They now look properly again.

Due to a Qt bug, installing Qt/PyQt from prebuilt binaries on systems with a very old libxcb-utils version (notably, Debian Stable, but not Ubuntu since 16.04 LTS) results in a setup which fails to start. This also affects the mkvenv.py script, which now includes a workaround for this case.

The open_url_instance.sh userscript now complains when socat is not installed, rather than silencing the error.

The example AppArmor profile in misc/ was outdated and written for the older QtWebKit backend. It is now updated to serve as an useful starting point with QtWebEngine.

When running :devtools on Fedora without the needed (optional) dependency installed, it was suggested to install qt5-webengine-devtools, which does not, in fact, exist. It’s now correctly suggested to install qt5-qtwebengine-devtools instead.

With Qt 5.15.2, lines/borders coming from the readability-js userscript were invisible. This is now fixed by changing the border color to grey (with all Qt versions).

Due to changes in the underlying Chromium, the colors.webpage.prefers_color_scheme_dark setting broke with Qt 5.15.2. It now works properly again.

A bug in the pkg_resources module used by qutebrowser caused deprecation warnings to appear on start with Python 3.9 on some setups. Those are now hidden.

Minor performance improvements.

Fix for various functionality breaking in private windows with v1.14.0, after the last private window is closed. This includes:

The content.media_capture setting got split up into three more fine-grained settings, content.media.audio_capture, .video_capture and .audio_video_capture. Before this change, answering "always" to a prompt about e.g. audio capturing would set the content.media_capture setting, which would also allow the same website to capture video on a future visit. Now every prompt will set the appropriate setting, though existing content.media_capture settings in autoconfig.yml will be migrated to set all three settings. To review/change previously granted permissions, use :config-diff and e.g. :config-unset -u example.org content.media.video_capture.

The main window’s (invisible) background color is now set to transparent. This allows using the alpha channel in statusbar/tabbar colors to get a partially transparent qutebrowser window on a setup which supports doing so.

If QtWebEngine is compiled with PipeWire support and libpipewire is installed, qutebrowser will now support screen sharing on Wayland. Note that QtWebEngine 5.15.1 is needed.

When :undo is used with a count, it now reopens the count-th to last tab instead of the last one. The depth can instead be passed as an argument, which is also completed.

The default completion.timestamp_format now also shows the time.

:back and :forward now take an optional index which is completed using the current tab’s history.

The time a website in a tab was visited is now saved/restored in sessions.

When attempting to download a file to a location for which there’s already a still-running download, a confirmation prompt is now displayed.

:completion-item-focus now understands next-page and prev-page with corresponding <PgDown> / <PgUp> default bindings.

When the last private window is closed, all private browsing data is now cleared.

When config.source(...) is used with a --config-py argument given, qutebrowser used to search relative files in the config basedir, leading to them not being found when using a shared config.py for different basedirs. Instead, they are now searched relative to the given config.py file.

navigate prev ([[) and navigate next (]]) now recognize links with nav-prev and nav-next classes, such as those used by the Hugo static site generator.

When tabs.favicons is disabled but tabs.tabs_are_windows is set, the window icon is still set to the page’s favicon now.

The --asciidoc argument to src2asciidoc.py and build_release.py now only takes the path to asciidoc.py, using the current Python interpreter by default. To configure the Python interpreter as well, use --asciidoc-python path/to/python --asciidoc path/to/asciidoc.py instead of the former --asciidoc path/to/python path/to/asciidoc.py.

Dark mode (colors.webpage.darkmode.*) is now supported with Qt 5.15.2 (which is not released yet).

The default for the darkmode policy.images setting is now set to smart which fixes issues with e.g. formulas on Wikipedia.

The readability-js userscript now adds some CSS to improve the reader mode styling in various scenarios:

The readability-js userscript now supports hint userscript mode.

New argument strip for :navigate which removes queries and fragments from the current URL.

:undo now has a new -w / --window argument, which can be used to restore closed windows (rather than tabs). This is bound to U by default.

:jseval can now take javascript:... URLs via a new --url flag.

New replacement {aligned_index} for tabs.title.format and format_pinned which behaves like {index}, but space-pads the index based on the total numbers of tabs. This can be used to get aligned tab texts with vertical tabs.

New command :devtools-focus (bound to wIf) to toggle keyboard focus between the devtools and web page.

The --target argument to qutebrowser now understands a new private-window value, which can be used to open a private window in an existing instance from the commandline.

The :download-open command now has a new --dir flag, which can be used to open the directory containing the downloaded file. An entry to do the same was also added to the context menu.

Messages are now wrapped when they are too long to be displayed on a single line.

New possible --debug-flag values:

A URL pattern with a *. host was considered valid and matched all hosts. Due to keybindings like tsH toggling scripts for *://*.{url:host}/*, invoking them on pages without a host (e.g. about:blank) could result in accidentally allowing/blocking JavaScript for all pages. Such patterns are now considered invalid, with existing patterns being automatically removed from autoconfig.yml.

When scrolling.bar was set to overlay (the default), qutebrowser would internally override any enable-features=... flags passed via qt.args or --qt-flag. It now correctly combines existing enable-feature flags with internal ones.

Elements with an inherited contenteditable attribute now trigger insert mode and get hints assigned correctly.

When checkmarks, radio buttons and some other elements are styled via the Bootstrap CSS framework, they now get hints correctly.

When the session file isn’t writable when qutebrowser exits, an error is now logged instead of crashing.

When using -m with the qute-lastpass userscript, it accidentally matched URLs containing the match as substring. This is now fixed.

When a filename is derived from a page’s title, it’s now shortened to the maximum filename length permitted by the filesystem.

:enter-mode register crashed since v1.13.0, it now displays an error instead.

With the QtWebKit backend, webpage resources loading certain invalid URLs could cause a crash, which is now fixed.

When :config-edit is used but no config.py exists yet, the file is now created (and watched for changes properly) before spawning the external editor.

When hint mode was entered from outside normal mode, the status bar was empty instead of displaying the proper text. This is now fixed.

When entering different modes too quickly (e.g. pressing fV), the statusbar could end up in a confusing state. This is now fixed.

When qutebrowser quits, running downloads are now cancelled properly.

The site-specific quirk for web.whatsapp.com has been updated to work after recent changes in WhatsApp.

Highlighting in the completion now works properly when UTF-16 surrogate pairs (such as emoji) are involved.

When a windowed inspector is clicked, insert mode now isn’t entered anymore.

When :undo is used to re-open a tab, but tabs.tabs_are_windows was set between closing and undoing the close, qutebrowser crashed. This is now fixed.

With QtWebEngine 5.15.0, setting the darkmode image policy to smart leads to renderer process crashes. The offending setting value is now ignored with a warning.

Fixes for the qute-pass userscript:

With Qt 5.14, shared workers are now disabled. This works around a crash in QtWebEngine on certain sites (like the Epic Games Store or the Unreal Engine page). On older versions, you can get the same effect by doing :set qt.args "['disable-shared-workers']" and :restart (or set the setting in your config.py).

When a window is closed, the tab it contains are now correctly shut down (closing e.g. any dialogs which are still open for those tabs).

The Qt 5.15 session workaround now loads the correct (rather than the last) page when :back was used before saving a session.

In certain situations on Windows, qutebrowser fails to find the username of the user launching qutebrowser (most likely due to a bug in the application launching it). When this happens, an error is now displayed instead of crashing.

Certain autoconfig.yml with an invalid structure could lead to crashes, which are now fixed.

Generating docs with asciidoc2html.py (e.g. via mkvenv.py) now works correctly without Pygments being installed system-wide.

Ever since Qt 5.9, when input.mouse.rocker_gestures was enabled, the context menu still was shown when clicking the right mouse button, thus preventing the rocker gestures. This is now fixed.

Clicking the inspector switched from existing modes (such as passthrough) to normal mode since v1.13.0. Now insert mode is only entered when the inspector is clicked in normal mode.

Pulseaudio now shows qutebrowser’s audio streams as qutebrowser correctly, rather than showing them as Chromium with some Qt versions.

If :help was called with a deprecated command (e.g. :help :inspector), the help page would show despite deprecated commands not being documented. This now shows an error instead.

The qute-lastpass userscript now filters out duplicate entries with --merge-candidates.

The :inspector command is deprecated and has been replaced by a new :devtools command (see below).

The :debug-log-level command was removed as it’s replaced by the new logging.level.console setting.

The qute://plainlog special page got replaced by qute://log?plain - the names of those pages is considered an implementation detail, and :messages --plain should be used instead.

Changes to commands:

Changes to settings:

New handling of bindings in hint mode which fixes various bugs and allows for single-letter keybindings in hint mode.

The statusbar now shows partial keychains in all modes (e.g. while hinting).

New t[Cc][Hh] default bindings which work similarly to the t[Ss][Hh] bindings for JavaScript but toggle cookie permissions.

The tor_identity userscript now takes the password via a -p flag and has a new -c flag to customize the Tor control port.

Small performance improvements.

New settings:

New :devtools command (replacing :inspector) with various improved functionality:

Crash when tabs.focus_stack_size is set to -1.

Crash when a pdf.js file for PDF.js exists, but viewer.html does not.

Crash when :completion-item-yank --sel is used on a platform without primary selection support (e.g. Windows/macOS).

Crash when there’s a feature permission request from Qt with an invalid URL (which happens due to a Qt bug with Qt 5.15 in private browsing mode).

Crash in rare cases where QtWebKit/QtWebEngine imports fail in unexpected ways.

Crash when something removed qutebrowser’s IPC socket file and it’s been running for 6 hours.

:config-write-py now works with paths starting with ~/... again.

New site-specific quirk for a missing globalThis in Qt ⇐ 5.12 on Reddit and Spotify.

When ; is added to hints.chars, using hint labels containing ;; now works properly.

Hint letters outside of ASCII should now work.

When bindings.key_mappings is used with hints, it now works properly with letters outside of ASCII as well.

With Qt 5.15, the audible/muted indicators are not updated properly due to a Qt bug. This release adds a workaround so that at least the muted indicator is shown properly.

As a workaround for crashes with QtWebEngine versions between 5.12 and 5.14 (inclusive), changing the user agent (content.headers.user_agent) exposed to JS now requires a restart. The corresponding HTTP header is not affected.

tox -e mkvenv which was deprecated in qutebrowser v1.10.0 is now removed. Use the mkvenv.py script instead.

Support for using config.bind(key, None) in config.py to unbind a key was deprecated in v1.8.2 and is now removed. Use config.unbind(key) instead.

:yank markdown was deprecated in v1.7.0 and is now removed. Use :yank inline [{title}]({url}) instead.

New :debug-keytester command, which shows a "key tester" widget. Previously, that was only available as a separate application via python3 -m scripts.keytester.

New :config-diff command which opens the qute://configdiff page.

New --debug-flag log-cookies to log cookies to the debug log.

New colors.contextmenu.disabled.{fg,bg} settings to customize colors for disabled items in the context menu.

New line selection mode (:toggle-selection --line), bound to Shift-V in caret mode.

New colors.webpage.darkmode.* settings to control Chromium’s dark mode. Note that those settings only work with QtWebEngine on Qt >= 5.14 and require a restart of qutebrowser.

Windows and macOS releases now ship Qt 5.15, which is based on Chromium 80.0.3987.163 with security fixes up to 81.0.4044.138.

The content.cookies.accept setting now accepts URL patterns.

Tests are now included in release tarballs. Note that only running them with the exact dependencies listed in misc/requirements/requirements-tests.txt{,-raw} is supported.

The :tab-focus command now has completion for tabs in the current window.

The bindings.key_mappings setting now maps <Ctrl+I> to the tab key by default.

:tab-give --private now detaches a tab into a new private window.

Using :open -s now only rewrites http:// in URLs to https://, not other schemes like qute://.

When an unhandled exception happens in certain parts of the code (outside of the main thread), qutebrowser did crash or freeze when trying to show its exception handler. This is now fixed.

:inspector now works correctly when cookies are disabled globally.

Added workaround for a (Gentoo?) PyQt/packaging issue related to the QWebEngineFindTextResult handling added in v1.11.0.

When entering caret selection mode (v, v) very early before a page is loaded, an error is now shown instead of a crash happening.

The workaround for session loading with Qt 5.15 now handles sessions.lazy_restore so that the saved page is loaded instead of the "stub" page with no possibility to get to the web page.

A site specific quirk to allow typing accented characters on Google Docs was active for docs.google.com, but not drive.google.com. It is now applied for both subdomains.

With older graphics hardware (OpenGL < 4.3) with Qt 5.14 on Wayland, WebGL causes segfaults. Now qutebrowser detects that combination and suggests to disable WebGL or use XWayland.

CVE-2020-11054: After a certificate error was overridden by the user, qutebrowser displays the URL as yellow (colors.statusbar.url.warn.fg). However, when the affected website was subsequently loaded again, the URL was mistakenly displayed as green (colors.statusbar.url.success_https). While the user already has seen a certificate error prompt at this point (or set content.ssl_strict to false which is not recommended), this could still provide a false sense of security. This is now fixed.

New settings:

New placeholders for url.searchengines values:

First adaptions to Qt 5.15, including a stop-gap measure for session loading not working properly with it.

Searching now wraps around the page by default with QtWebKit (where it didn’t before). Set search.wrap to false to restore the old behavior.

The {} placeholder for search engines (the url.searchengines setting) now does not quote slashes anymore, but other characters typically encoded in URLs still get encoded. This matches the behavior of search engines in Chromium. To revert to the old behavior, use {quoted} instead.

The content.windowed_fullscreen setting got renamed to content.fullscreen.window.

Mouse-wheel scrolling is now prevented while hints are active.

Changes to userscripts:

The dictcli.py script now shows better error messages.

Various improvements to the mkvenv.py script (mainly useful for development).

Minor performance improvements.

A warning about old Qt versions is now also shown with Qt 5.9 and 5.10, as support for Qt < 5.11 will be dropped in qutebrowser v2.0.

unsafeWindow is now defined for Greasemonkey scripts with QtWebKit.

The proxied window global is now shared between different Greasemonkey scripts (but still separate from the page’s window), to match the original Greasemonkey implementation.

The --output-messages (-m) flag added in v1.9.0 now also works correctly when using :spawn --userscript.

:version and --version now don’t crash if there’s an (invalid) /etc/os-release file which has non-comment lines without a = character.

Scripts in scripts/ now report errors to stderr correctly, instead of using stdout.

Windows and macOS releases now bundle Qt 5.14.2, including security fixes up to Chromium 80.0.3987.132.

The WhatsApp workaround now also works when using WhatsApp in languages other than English.

The mkvenv.py script now also works properly on Windows.

Crash when saving data fails during shutdown (which was a regression introduced in v1.9.0).

Error while reading config.py when fonts.tabs or fonts.debug_console is set to a value including default_size.

When a state file contains invalid UTF-8 data, a proper error is now displayed.

When the Qt version changes (and also on the first start of v1.10.1 on Qt 5.14), service workers registered by websites are now deleted. This is done as a workaround for QtWebEngine issues causing crashes when visiting pages using service workers (such as Google Mail/Drive). No persistent data should be affected as websites can re-register their service workers, but a (single) backup is kept at webengine/Service Worker-bak in qutebrowser’s data directory.

Better output on stdout when config errors occur.

The mkvenv.py now ensures the latest versions of setuptools and wheel are installed in the virtual environment, which should speed up installation and fix install issues.

The default for colors.statusbar.command.private.bg has been changed to a slightly different gray, as a workaround for a Qt issue where the cursor was invisible in that case.

New colors.webpage.prefers_color_scheme_dark setting which allows forcing prefers-color-scheme: dark colors for websites (QtWebEngine with Qt 5.14 or newer).

New fonts.default_size setting which can be used to set a bigger font size for all UI fonts.

The fonts.monospace setting has been removed and replaced by fonts.default_family. The new default_family setting is improved in various ways:

If monospace is now used in a font value, it’s used literally and not replaced anymore. Instead, default_family is replaced as explained above.

The default content.headers.accept_language value now adds a ;q=0.9 classifier which should make the value sent more in-line with what other browsers do.

The qute-pass userscript now has a new --mode gopass switch which uses gopass rather than pass.

The tox -e mkvenv (or mkvenv-pypi) way of installing qutebrowser is now replaced by a mkvenv.py script. See the updated install instructions for details.

macOS and Windows releases now ship with Qt/QtWebEngine 5.14.1

When quitting qutebrowser, components are now cleaned up differently. This should fix certain (rare) segmentation faults and exceptions when quitting, especially with the new exit scheme introduced in in PyQt5 5.13.1.

Added a workaround for per-domain settings (e.g. a JavaScript whitelist) not being applied in some scenarios with Qt 5.13 and above.

Added additional site-specific quirk for WhatsApp Web.

The qute-pass userscript now works correctly when a PASSWORD_STORE_DIR ending with a trailing slash is given.

Initial support for Qt 5.14.

New content.site_specific_quirks setting which enables workarounds for websites with broken user agent parsing (enabled by default, see the "Fixed" section for fixed websites).

New qt.force_platformtheme setting to force Qt to use a given platform theme.

New tabs.tooltips setting which can be used to disable hover tooltips for tabs.

New settings to configure the appearance of context menus:

The macOS binaries now require macOS 10.13 High Sierra or newer. Support for macOS 10.12 Sierra has been dropped.

The content.headers.user_agent setting now is a format string with the default value resembling the behavior of it being set to null before. This slightly changes the sent user agent for QtWebKit: Instead of mentioning qutebrowser and its version it now mentions the Qt version.

The qute-pass userscript now has a new --extra-url-suffixes (-s) argument which passes extra URL suffixes to the tldextract library.

A stack is now used for :tab-focus last rather than just saving one tab. Additionally, :tab-focus now understands stack-prev and stack-next arguments to traverse that stack.

:hint now has a new right-click target which allows right-clicking elements via hints.

The Terminus font has been removed from the default monospace fonts since it caused trouble with HighDPI setups. To get it back, add either "xos4 Terminus" or Terminus (depending on fontconfig version) to the beginning of the fonts.monospace setting.

As a workaround for a Qt bug causing a segfault, desktop sharing is now automatically rejected on Qt versions before 5.13.2. Note that screen sharing still won’t work on Linux before Qt 5.14.

Comment lines in quickmarks/bookmarks files are now ignored. However, note that qutebrowser will overwrite those files if bookmark/quickmark commands are used.

Reopening PDF.js pages from e.g. a session file will now re-download and display those PDFs.

Improved behavior when using :open-download in a sandboxed environment (KDE Flatpak).

qutebrowser now enables the new PyQt exit scheme, which should result in things being cleaned up more properly (e.g. cookies being saved even without a timeout) on PyQt 5.13.1 and newer.

The :spawn command has a new -m / --output-messages argument which shows qutebrowser messages based on a command’s standard output/error.

Improved insert mode detection for some CodeMirror usages (e.g. in JupyterLab and Jupyter Notebook).

If JavaScript is disabled globally, file://* now doesn’t automatically have it enabled anymore. Run :set -u file://* content.javascript.enabled true to restore the previous behavior.

Settings with URL patterns can now be used to affect the behavior of the QtWebEngine inspector. Note that the underlying URL is chrome-devtools://* from Qt 5.11 to Qt 5.13, but devtools://* with Qt 5.14.

Improvements when tabs.tabs_are_windows is set:

Improved parsing in some corner cases for the QtFont type (used for fonts.tabs and fonts.debug_console).

Performance improvements for the following areas:

Downloads (e.g. via :download) now see the same user agent header as webpages, which fixes cases where overly restrictive servers/WAFs closed the connection before.

dictcli.py now works correctly on Windows again.

The logic for :restart has been revisited, which should fix issues with relative basedirs.

Remaining issues related to Python 3.8 are now fixed (mostly warnings, especially on QtWebKit).

Workaround for a Qt bug where a page never finishes loading with a non-overridable TLS error (e.g. due to HSTS).

The qute://configdiff page now doesn’t show built-in settings (e.g. javascript being enabled for qute:// and chrome:// pages) anymore.

The qute-lastpass userscript now stops prompting for passwords when cancelling the password input.

The tab hover text now shows ampersands (&) correctly.

With QtWebEngine and Qt >= 5.11, the inspector now shows its icons correctly even if loading of images is disabled via the content.images setting.

Entering a very long string (over 50k characters) in the completion used to crash, now it shows an error message instead.

Various improvements for URL/searchengine detection:

New "site specific quirks", which work around some broken websites:

Segmentation fault introduced in v1.8.2 when a tab gets closed immediately after it has finished loading (e.g. with certain login flows).

Windows/macOS releases now ship with Qt 5.12.6. This includes security fixes up to Chromium 77.0.3865.120 plus a security fix for CVE-2019-13720 from Chromium 78.

Unbinding keys via config.bind(key, None) accidentally worked in v1.7.0 but raises an exception in v1.8.0. It now works again, but is deprecated and shows an error. Note that :config-py-write did write such invalid lines before v1.8.0, so existing config files might need adjustments.

The readability-js userscript now handles encodings correctly (which it didn’t before for some websites).

<Shift-Insert> can now be used to paste text starting with a hyphen.

Following hints via the number keypad now works properly again.

Errors while reading the state file are now displayed instead of causing a crash.

Crash when using :debug-log-level without a console attached.

Downloads are now hidden properly when the browser is in fullscreen mode.

Crash when setting colors.webpage.bg to an empty value with QtWebKit.

Crash when the history database file is not a proper sqlite database.

Workaround for missing/broken error pages on Debian.

A deprecation warning (caused by pywin32) about the imp module on Windows is now hidden.

No code changes - this release only repackages the Windows/macOS releases due to issues with the v1.8.0 release.

Updated dependencies for Windows/macOS releases:

New userscripts:

The statusbar text for passthrough mode now shows all configured bindings to leave the mode, not only one.

When :config-source is used with a relative filename, the file is now searched in the config directory instead of the current working directory.

HTML5 inputs with date/time types now enter insert mode when selected.

dictcli.py now shows where dictionaries are installed to and complains when running it as root if doing so would result in a wrong installation path.

The Makefile now can also run setup.py build when invoked without a target.

Changes to userscripts:

Performance improvements in various areas:

:version now shows details about the loaded autoconfig.yml/config.py.

Hosts are now additionally looked up including their ports in netrc files.

With Qt 5.10 or newer, qutebrowser now doesn’t force software rendering with Nouveau drivers anymore. However, QtWebEngine/Chromium still do so.

The XSS Auditor is now disabled by default (content.xss_auditing = false). This reflects a similar change in Chromium, see their XSS Auditor Design Document for details.

:config-write-py now correctly writes config.unbind(...) lines (instead of config.bind(..., None)) when unbinding a default keybinding.

Prevent repeat keyup events for JavaScript when a key is held down.

The Makefile now rebuilds the manpage correctly.

~/.config/qutebrowser/blocked-hosts can now also contain /etc/hosts-like lines, not just simple hostnames.

Restored compatibility with Jinja2 2.8 (e.g. used on Debian Stretch or Ubuntu 16.04 LTS).

Fixed implicit type conversion warning with Python 3.8.

The desktop file now sets StartupWMClass correctly, so the qutebrowser icon is no longer shown twice in the Gnome dock when pinned.

Bindings involving keys which need the AltGr key now work properly.

Fixed crash (caused by a Qt bug) when typing characters above the Unicode BMP (such as certain emoji or CJK characters).

dictcli.py now works properly again.

Shift can now be used while typing hint keystrings, which e.g. allows typing number hints on French keyboards.

With rapid hinting in number mode, backspace now edits the filter text after following a hint.

A certain type of error ("locking protocol") while initializing sqlite now isn’t handled as crash anymore.

Crash when showing a permission request in certain scenarios.

At least Python 3.5.2 is now required to run qutebrowser, support for 3.5.0 and 3.5.1 was dropped.

New settings:

New commands:

New commandline replacements:

The {title} field in tabs.title.format, tabs.title.format_pinned and window.title_format got renamed to {current_title} (mirroring {current_url}) in order to not conflict with the new {title} commandline replacement.

New delete target for :hint which removes the hinted element from the DOM.

New --config-py commandline argument to use a custom config.py file.

Qt 5.13: Support for notifications (shown via system tray).

Updated dependencies for Windows/macOS releases:

PyQt5 5.12.3 / PyQtWebEngine 5.12.1

Qt 5.12.4, which includes security fixes up to Chromium 74.0.3729.157

Python 3.7.4

OpenSSL 1.1.1

Note: This release includes Qt 5.12.4 instead of Qt 5.13.0 due to QTBUG-76913 causing frequent segfaults with Qt 5.13. After Qt 5.13.1 is released, qutebrowser v1.8.0 will be released with an updated Qt.

Completely revamped Windows installer which allows installing without admin permissions and allows setting qutebrowser as default browser.

The desktop file qutebrowser.desktop is now renamed to org.qutebrowser.qutebrowser.desktop.

Pinned tabs now always show a favicon (even if the site doesn’t provide one) when shrinking.

Setting downloads.location.directory now changes the directory displayed in the download prompt even if downloads.location.remember is set.

The yank command gained a new inline argument, which allows to e.g. use :yank inline [{title}]({url}).

Duplicate consecutive history entries with the same URL are now ignored.

More detailed error messages when spawning a process failed.

The content.pdfjs setting now supports domain patterns.

Improved process status output with :spawn -o.

The colors.tabs.bar.bg setting is now of type QssColor and thus supports gradients.

The :fullscreen command now understands a new --enter flag which causes it to always enter fullscreen instead of toggling the current state.

--debug-flag stack is now needed to show stack traces on renderer process crashes.

--debug-flag chromium can be used to easily turn on verbose Chromium logging.

For runtime data (such as the IPC socket), a proper runtime path is now used on BSD; only macOS/Windows continue to use the temporary directory.

PDF.js is now also searched in /app/share/pdf.js/ (for Flatpak)

Permission prompts can now be answered with Y (:prompt-accept --save yes) and N (:prompt-accept --save no) to save the answer as a per-domain setting.

content.dns_prefetch is now turned off by default, as it causes crashes inside QtWebEngine.

The (still unofficial) interceptor plugin API now contains resource_type for a request and allows redirecting requests.

:bookmark-remove now shows a message for consistency with :bookmark-add.

Very early segfaults are now also caught by the crash handler.

The appdata XML now contains proper release information and an (empty) OARS content rating.

Improved Linux distribution detection.

Qt 5.13: Request filtering now happens in the UI rather than IO thread.

Qt 5.13: Support for PDFium (Chromium’s PDF viewer) is disabled for now so that PDFs can still be downloaded (or shown with PDF.js) properly.

Various performance improvements (e.g. for showing hints or the :open completion).

:yank markdown got deprecated, as :yank inline [{title}]({url}) can now be used instead.

Various QtWebEngine load signals are now handled differently, which should fix issues with insert mode being left while typing on sites like Google Translate.

Race condition causing a colored statusbar in normal mode when entering/exiting caret mode quickly.

Using 100% for a hue in a hsv(...) config value now corresponds to 359 (rather than 255), matching the fixed behavior in Qt 5.13.

Chaining commands with ;; used to abort with some failing commands. It now runs the second command no matter whether the first one succeeded or not.

Handling of profiles and private windows (and resulting crashes with Qt 5.12.2).

Fixes for corner-cases when using :navigate increment/decrement.

The type for the colors.hints.match.fg setting was changed to QtColor. Gradients were never supported for this setting, and with this change, values like rgb(0, 0, 0) now work as well.

Permission prompts now show a properly normalized URL with QtWebKit.

Crash on start when PyQt was built without SSL support with Qt >= 5.12.

Minor memory leaks.

Crash when hinting and changing/closing the tab before hints are displayed.

Crash on redirects with Qt 5.13.

Hide bogus AA_ShareOpenGLContexts warning with Qt 5.12.4.

Workaround for renderer process crashes with Qt 5.12.4. If you’re unable to update, you can remove ~/.cache/qutebrowser for the same result.

Windows/macOS releases now ship with Qt 5.12.3, which includes security fixes up to Chromium 73.0.3683.75.

Crash when SQL errors occur while using the completion.

Crash when cancelling a download prompt started in an already closed window.

Crash when many prompts are opened at the same time.

Running without Qt installed now displays a proper error again.

High CPU usage when using the keyhint widget with a low delay.

Crash with Qt >= 5.14 on redirects.

Windows/macOS releases now ship with Qt 5.12.2, which includes security fixes up to Chromium 72.0.3626.121 (including CVE-2019-5786 which is known to be exploited in the wild).

Crash when using :config-{dict,list}-{add,remove} with an invalid setting.

Functionality like hinting on pages with an element with ID _qutebrowser (such as qutebrowser.org) on Qt 5.12.

The .desktop file in v1.6.0 was missing the "Actions" key, which is now fixed.

The SVG icon now has a size of 256x256px set to comply with freedesktop standards.

Setting colors.statusbar.*.bg to a gradient now has the expected effect of the gradient spanning the entire statusbar.

New settings:

New config manipulation commands:

New :yank markdown feature which yanks the current URL and title in markdown format.

Support for new QtWebEngine features in Qt 5.12:

Various changes to the Windows and macOS builds:

:q now closes the current window instead of quitting qutebrowser completely (:close), while :qa quits (:quit). The behavior of :wq remains unchanged (:quit --save), as closing a window while saving the session doesn’t make sense.

Completion highlighting is now done differently (using QSyntaxHighlighter), which should fix some highlighting corner-cases.

The QtColor config type now also understands colors like rgb(...).

:yank now has a --quiet option which causes it to not display a message.

The :open completion now also shows search engines by default.

The content.host_blocking.enabled setting now supports URL patterns, so the adblocker can be disabled on a given page.

Elements with a tabindex attribute now also get hints by default.

Various small performance improvements for hints and the completion.

The Wayland check for QtWebEngine is now disabled on Qt >= 5.11.2, as those versions should work without any issues.

The JavaScript console object is now available in PAC files.

PAC proxies currently don’t work properly on QtWebEngine (and never did), so an error is now shown when trying to configure a PAC proxy.

The metainfo file qutebrowser.appdata.xml is now renamed to org.qutebrowser.qutebrowser.appdata.xml.

The qute-pass userscript now understands domains in gpg filenames in addition to directory names.

The autocompletion for content.headers.user_agent got updated to only include the default and Chrome, as setting the UA to Firefox has various bad side-effects.

Combining Qt 5.12 with an older PyQt can lead to issues, so a warning is now shown when starting qutebrowser with that combination.

Invalid world IDs now get rejected for :jseval and GreaseMonkey scripts.

When websites suggest download filenames with invalid characters, those are now correctly replaced.

Invalid hint length calculation in certain rare cases.

Dragging tabs in the tab bar (which was broken in v1.5.0)

Using Shift-Home in command mode now works properly.

Workaround for a Qt bug which prevented content.cookies.accept = no-3rdparty from working properly on some pages like GMail. However, the default for content.cookies.accept is still all to be in line with what other browsers do.

:navigate not incrementing in anchors or queries.

Crash when trying to use a proxy requiring authentication with QtWebKit.

Slashes in search terms are now percent-escaped.

When scrolling.bar = True was set in versions before v1.5.0, this now correctly gets migrated to always instead of when-searching.

Completion highlighting now works again on Qt 5.11.3 and 5.12.1.

The non-standard header X-Do-Not-Track is no longer sent.

PAC proxies were never correctly supported with QtWebEngine, but are now explicitly disallowed.

macOS: Context menus for download items now show in the correct macOS style.

Issues with fullscreen handling when exiting a video player.

Various fixes for Qt 5.12 issues:

The content.cookies.accept setting is now set to all instead of no-3rdparty by default, as no-3rdparty breaks various pages such as GMail.

Flickering when opening/closing tabs (as soon as more than 10 are open) on some pages.

PDF.js is now bundled again with the macOS/Windows release.

PDF.js is now searched in the correct path (if not installed system-wide) instead of hardcoding ~/.local/share/qutebrowser.

Improved logging for PDF.js resources which fail to load.

Crash when closing a tab after doing a search.

Tabs appearing when hidden after e.g. closing tabs.

Rewritten PDF.js support:

New settings:

Running qutebrowser with QtWebKit or Qt < 5.9 now shows a warning (only once), as support for those is going to be removed in a future release.

New t[iI][hHu] default bindings (similar to tsh etc.) to toggle images.

The qute-pass userscript now has optional OTP support.

When :spawn --userscript is called with a count, that count is now passed to userscripts as $QUTE_COUNT.

Windows and macOS releases now bundle Python 3.7, PyQt 5.11.3 and Qt 5.11.2. QtWebEngine includes security fixes up to Chromium 68.0.3440.75 and various other fixes.

Various performance improvements when many tabs are opened.

The content.headers.referer setting now works on QtWebEngine.

The :repeat command now takes a count which is multiplied with the given "times" argument.

The default keybinding to leave passthrough mode was changed from <Ctrl-V> to <Shift-Escape>, which makes pasting from the clipboard easier in passthrough mode and is also unlikely to conflict with webpage bindings.

The app_id is now set to qutebrowser for Wayland.

Command or Cmd can now be used (instead of Meta) to map the Command key on macOS.

Using :set option now shows the value of the setting (like :set option? already did).

The completion.web_history_max_items setting got renamed to completion.web_history.max_items.

The Makefile shipped with qutebrowser now supports overriding variables DATADIR and MANDIR.

Regenerating completion history now shows a progress dialog.

The content.autoplay setting now supports URL patterns on Qt >= 5.11.

The content.host_blocking.whitelist setting now takes a list of URL patterns instead of globs.

In passthrough mode, Ctrl + Mousewheel now also gets passed through to the page instead of zooming.

Editing text in an external editor now simulates a JS "input" event, which improves compatibility with websites reacting via JS to input.

The qute://settings page is now properly sorted on Python 3.5.

:zoom, :zoom-in and :zoom-out now have a --quiet switch which causes them to not display a message.

The scrolling.bar setting now takes three values instead of being a boolean: always, never, and when-searching (which only displays it while a search is active).

@@ now repeats the last run macro.

The content.host_blocking.lists setting now accepts a file:// URL to a directory, and reads all files in that directory.

The :tab-give and :tab-take command now have a new flag --keep which causes them to keep the old tab around.

:navigate now clears the URL query.

qute:// pages now work properly on Qt 5.11.2

Error when passing a substring with spaces to :tab-take.

Greasemonkey scripts which start with a UTF-8 BOM are now handled correctly.

When no documentation has been generated, the plaintext documentation now can be shown for more files such as qute://help/userscripts.html.

Crash when doing initial run on Wayland without XWayland.

Crash when trying to load an empty session file.

:hint with an invalid --mode= value now shows a proper error.

Rare crash on Qt 5.11.2 when clicking on <select> elements.

Rare crash related to the completion.

Support for importing pre-v1.0.0 history files has been removed.

The content.webrtc_public_interfaces_only setting has been removed and replaced by content.webrtc_ip_handling_policy.

The content.xss_auditing setting is now enabled by default, to mirror Chromium’s rather than Qt’s default behavior.

Long URLs in the statusbar are now elided at the end rather than in the middle, to make sure the hostname is completely visible whenever possible.

Crash in Qt 5.7.1 when a website uses window.print().

The workaround for Nouveau graphic drivers now works properly again.

Crash when using :follow-selected with a link which is outside of the view.

Workaround for windows not showing as urgent with some window managers (like i3).

Crash when opening URLs with some unicode characters (IDNA 2008). Those URLs still won’t open though, due to missing support in Qt.

Crash when a download directory which can’t be created is configured.

Crash in the importer.py script when importing Chrome bookmarks from newer Chrome versions.

The content.webrtc_public_interfaces_only option didn’t work on Qt 5.11 previously (it now does). Note it still does not work on Qt 5.10 (due to a Qt bug) and Qt < 5.9.2.

Repeated escaping of entries in qute://log when refreshing page.

The host blocker doesn’t block 0.0.0.0 anymore.

Crash when using :// as URL pattern.

The :buffer completion now sorts tabs with indices >= 10 correctly again.

CVE-2018-10895: Fix CSRF issue on the qute://settings page, leading to possible arbitrary code execution. See the related GitHub issue for details: https://github.com/qutebrowser/qutebrowser/issues/4060

Rare crash when an error occurs in downloads.

Newlines are now stripped from the :version pastebin URL.

There’s a new mkvenv-pypi-old environment in tox.ini which installs an older Qt, which is needed on Ubuntu 16.04.

Worked around a Qt issue which redirects to a chrome-error:// page when trying to use U2F.

The link_pyqt.py script now works correctly with PyQt 5.11.

The Windows installer now uninstalls the old version before installing the new one, fixing issues with qutebrowser not starting after installing v1.4.0 over v1.3.3.

Support for the bundled sip module in PyQt 5.11 and other changes in Qt/PyQt 5.11.x.

New --debug-flag log-requests to log requests to the debug log for debugging.

New --first flag for :hint (bound to gi for inputs) which automatically selects the first hint.

New input.escape_quits_reporter setting which can be used to avoid accidentally quitting the crash reporter when pressing escape.

New qute-lastpass userscript which uses the LastPass CLI to fill passwords.

The Makefile now installs a /usr/share/metainfo/qutebrowser.appdata.xml file.

QtWebEngine: Support for printing from webpages via window.print.

QtWebEngine: Support for muting tabs:

QtWebEngine: Support for content.cookies.accept with third-party cookies blocked by default (requires Qt 5.11).

QtWebEngine: New settings:

The following settings now support URL patterns:

The Windows/macOS releases now bundle Qt 5.11.1 which is based on Chromium 65.0.3325.151 with security fixes up to Chromium 67.0.3396.87.

New short flags for commandline arguments: -B and -T for --basedir and --temp-basedir; -d and -D for --debug and --debug-flag.

Deleting history items via :history-clear or :completion-item-del now also removes that URL from QtWebEngine’s visited links.

There’s now completion for commands taking a variable count of arguments (like :config-cycle).

QtWebEngine: On Qt 5.11.1, no reloads are needed anymore when switching between pages with changed settings (e.g. content.javascript.enabled).

The qt.force_software_rendering setting changed from a boolean to taking different values (software-opengl, qt-quick and chromium) for different kinds of software rendering workarounds.

On Qt 5.11, using wayland with QtWebEngine is now possible when using software rendering.

GreaseMonkey scripts now get their own global scope (based on the page’s one), which allows scripts like OneeChan to work.

Rapid hinting is now supported with the yank and yank-primary targets, copying newline-separated links.

QtWebEngine: On Qt 5.11, the developer tools (inspector) can now be used securely and without requiring the --enable-webengine-inspector option.

The <Enter> key (:follow-selected) now follows the currently focused element if there’s no selection.

The --logfilter argument now can be prepended with an exclamation mark (e.g. --logfilter '!init,destroy') to invert the filter.

:view-source now has a --pygments flag which uses the "old" way of rendering sources even with QtWebEngine.

Improved error messages when a setting needs a newer Qt version.

QtWebEngine: Various improvements to make the cursor more visible in caret browsing.

When a prompt is opened in insert/passthrough mode, the mode is restored after closing the prompt.

On Qt 5.10 or newer, dictionaries are now read from the qutebrowser data directory (e.g. ~/.local/share/qutebrowser) instead of /usr/share/qt. Existing dictionaries are copied over.

If an error while parsing ~/.netrc occurs, the cause of the error is now logged.

On Qt 5.9 or newer, certificate errors now show Chromium’s detailed error page.

Greasemonkey scripts now support a "@qute-js-world" tag to run them in a different JavaScript context.

Various subtle keyboard focus issues.

The security fix in v1.3.3 caused URLs with ampersands (www.example.com?one=1&two=2) to send the wrong arguments when clicked on the qute://history page.

Crash when opening a PDF page with PDF.js enabled (on QtWebKit), but no PDF.js installed.

Crash when closing a tab shortly after opening it.

No prebuilt binaries for 32-bit Windows are supplied anymore. This is due to Qt removing QtWebEngine support for those upstream. It might be possible to distribute 32-bit binaries again with Qt 5.12 in December, but that will only happen if it turns out enough people actually need 32-bit support.

:tab-detach which has been deprecated in v1.1.0 has been removed.

The content.developer_extras setting got removed. On QtWebKit, developer extras are now automatically enabled when opening the inspector.

CVE-2018-1000559: An XSS vulnerability on the qute://history page allowed websites to inject HTML into the page via a crafted title tag. This could allow them to steal your browsing history. If you’re currently unable to upgrade, avoid using :history. See the related GitHub issue for details: https://github.com/qutebrowser/qutebrowser/issues/4011.

Crash in a workaround for a Qt 5.11 bug in rare circumstances.

Workaround for a Qt bug which preserves searches between page loads.

In v1.3.2 a dependency on the PyQt5.QtQuickWidgets module was accidentally introduced. Since that module isn’t packaged everywhere, it’s been removed again.

QtWebEngine: Improved workaround for a bug in Qt 5.11 where only the top/bottom half of the window is used.

QtWebEngine: Work around a bug in Qt 5.11 where an endless loading-loop is triggered when clicking a link with an unknown scheme.

QtWebEngine: When switching between pages with changed settings, less unnecessary reloads are done now.

QtWebEngine: It’s now possible to open external links such as magnet:// or mailto: via hints.

Work around a bug in Qt 5.11 where only the top/bottom half of the window is used. This workaround is incomplete, but fixes the majority of the cases where this happens.

Work around keyboard focus issues with Qt 5.11.

Work around an issue in Qt 5.11 where e.g. activating JavaScript per-domain needed a manual reload in some cases.

Don’t crash when a ² key is pressed (e.g. on AZERTY keyboards).

Don’t crash when a tab is opened and quickly closed again.

New :scroll-to-anchor command to scroll to an anchor in the document.

New url.open_base_url option to open the base URL of a searchengine when no search term is given.

New tabs.min_width setting to configure the minimal width for tabs.

New userscripts:

QtWebEngine: Support for JavaScript Shared Web Workers have been disabled on Qt versions older than 5.11 because of security issues in in Chromium. You can get the same effect in earlier versions via :set qt.args ['disable-shared-workers']. An equivalent workaround is also contained in Qt 5.9.5 and 5.10.1.

The file dialog for downloads now has basic tab completion based on the entered text.

:version now shows OS information for POSIX OS other than Linux/macOS.

When there’s an error inserting the text from an external editor, a backup file is now saved.

The window.hide_wayland_decoration setting got renamed to window.hide_decoration and now also works outside of wayland.

The tabs.favicons.show setting now can take three values: 'always' (was True), 'never' (was False) and 'pinned' (to only show favicons for pinned tabs).

Hover tooltips on tabs now always show the webpage’s title.

The default value for content.host_blocking.lists was changed to only include Steven Black’s hosts-list which combines various sources.

Error messages when trying to wrap when tabs.wrap is False are now logged to debug instead of messages.

Using hints before a page is fully loaded is now possible again.

Selecting hints with the number keypad now works again.

Tab titles for tabs loaded from sessions should now really be correct instead of showing the URL.

Loading URLs with customized settings from a session now avoids an additional reload.

The window icon and title now get set correctly again.

The tabs.switching_delay setting now has a correct maximum value limit set.

The taskadd script now works properly when there’s multi-line output.

QtWebEngine: Worked around issues with GreaseMonkey/stylesheets not being loaded correctly in some situations.

The statusbar now more closely reflects the caret mode state.

The icon on Windows should now be displayed in a higher resolution.

The QtWebEngine development tools (inspector) now also work when JavaScript is disabled globally.

Building .exe files now works when upx is installed on the system.

The keyhint widget now shows the correct text for chained modifiers.

Loading GreaseMonkey scripts now also works with Jinja2 2.8 (e.g. on Debian Stable).

Adding styles with GreaseMonkey on fast sites now works properly.

Window ID 0 is now excluded properly from :tab-take completion.

A rare crash when cancelling a download has been fixed.

The Makefile (intended for packagers) now supports PREFIX properly.

The workaround for a black window with Nvidia graphics is now enabled on non-Linux systems (like FreeBSD) as well.

Initial support for Qt 5.11.

Checking for a new version after sending a crash report now works properly again.

@match in Greasemonkey scripts now more closely matches the proper pattern syntax.

Searching via / or ? now doesn’t handle any characters in a special way.

Fixed crash when trying to retry some failed downloads on QtWebEngine.

An invalid spellcheck dictionary filename now doesn’t crash anymore.

When no spellcheck dictionaries are configured, it’s now disabled internally. This works around an issue with entering special characters on Facebook messenger.

The macOS release now should work again on macOS 10.11 and newer.

qutebrowser now starts properly when the PyQt5 QOpenGLFunctions package wasn’t found.

The keybinding cheatsheet on the quickstart page is now loaded from a local qute:// URL again.

With "tox -e mkvenv-pypi", PyQt 5.10.0 is used again instead of Qt 5.10.1, because of an issue with Qt 5.10.1 which causes qutebrowser to fail to start ("Could not find QtWebEngineProcess").

Unbinding keys which were bound in older qutebrowser versions now doesn’t crash anymore.

Fixed a crash when reloading a page which wasn’t fully loaded with v1.2.0

Keys on the numeric keypad now fall back to the same bindings without Num+ if no Num+ binding was found.

Fixed hinting on some pages with Qt < 5.10.

Titles are now displayed correctly again for tabs which are cloned or loaded from sessions.

Shortcuts now correctly use Ctrl instead of Command on macOS again.

Initial implementation of per-domain settings:

New QtWebEngine features:

New flags for existing commands:

New special pages:

New settings:

New :prompt-yank command (bound to Alt-y by default) to yank URLs referenced in prompts.

The hostblock_blame script which was removed in v1.0 was updated for the new config and re-added.

New cycle-inputs.js script in scripts/ which can be used with :jseval -f to cycle through inputs.

Complete refactoring of key input handling, with various effects:

Improvements for GreaseMonkey support:

The sqlite history now uses write-ahead logging which should be a performance and stability improvement.

When an editor is spawned with :open-editor and :config-edit, the changes are now applied as soon as the file is saved in the editor.

The hist_importer.py script now only imports URL schemes qutebrowser can handle.

Deleting a prefix (:, / or ?) via backspace now leaves command mode.

Angular 1 elements and <summary>/<details> now get hints assigned.

:tab-only with pinned tabs now still closes unpinned tabs.

The url.incdec_segments option now also can take port as possible segment.

QtWebEngine: :view-source now uses Chromium’s view-source: scheme.

Tabs now show their full title as tooltip.

When there are multiple unknown keys in a autoconfig.yml, they now all get reported in one error.

More performance improvements when opening/closing many tabs.

The :version page now has a button to pastebin the information.

Replacements like {url} can now be escaped as {{url}}.

QtWebEngine bugfixes:

QtWebKit bugfixes:

URLs containing ampersands and other special chars are now shown correctly when filtering them in the completion.

:bookmark-add "" foo can now be used to save the current URL with a custom title.

:spawn -o now waits until the process has finished before trying to show the output. Previously, it incorrectly showed the previous output immediately.

Suspended pages now should always load the correct page when being un-suspended.

Exception types are now shown properly with :config-source and :config-edit.

When using :bookmark-add --toggle, bookmarks are now saved properly.

Crash when opening an invalid URL from an application on macOS.

Crash with an empty completion.timestamp_format.

Crash when completion.min_chars is set in some cases.

HTML/JS resource files are now read into RAM on start to avoid crashes when changing qutebrowser versions while it’s open.

Setting bindings.key_mappings to an empty value is now allowed.

Bindings to an empty commands are now ignored rather than crashing.

QUTE_SELECTED_HTML is now not set for userscripts anymore except when called via hints.

The qutebrowser_viewsource userscript has been removed as :view-source --edit can now be used.

The tabs.persist_mode_on_change setting has been removed and replaced by tabs.mode_on_change.

Windows/macOS releases now bundle Qt 5.10.1 which includes security fixes from Chromium up to version 64.0.3282.140.

QtWebEngine: Crash with Qt 5.10.1 when using :undo on some tabs.

Compatibility with Python 3.7

The Makefile now actually works.

Fixed crashes with Qt 5.10 when closing a tab before it finished loading.

Initial support for Greasemonkey scripts. There are still some rough edges, but many scripts should already work.

There’s now a misc/Makefile file in releases, which should help distributions which package qutebrowser, as they can run something like make -f misc/Makefile DESTDIR="$pkgdir" install now.

New fields for window.title_format and tabs.title.format:

New settings:

New commands:

New flags for existing commands:

New config.source(...) method for config.py to source another file.

New {line} and {column} replacements for editor.command to position the cursor correctly.

New qute-pass userscript as alternative to password_fill which allows selecting accounts via rofi or any other dmenu-compatile application.

New hist_importer.py script to import history from Firefox/Chromium.

Some settings got renamed:

Much improved user stylesheet handling for QtWebEngine which reduces flickering and updates immediately after setting a stylesheet.

High-DPI favicons are now used when available.

The asciidoc2html.py script now uses Pygments (which is already a dependency of qutebrowser) instead of source-highlight for syntax highlighting.

The :buffer command now doesn’t require quoting anymore, similar to :open.

The ‘importer.py` script was largely rewritten and now also supports importing from Firefox’ places.sqlite file and Chrome/Chromium profiles.

Various internal refactorings to use Python 3.5 and ECMAscript 6 features.

If the window.hide_wayland_decoration setting is False, but QT_WAYLAND_DISABLE_WINDOWDECORATION is set in the environment, the decorations are still hidden.

The install_dict.py script for QtWebEngine was renamed to dictcli.py and can now also upgrade dictionaries correctly.

:undo now can re-open multiple tabs after :tab-only was used.

:config-write-py with a relative path now puts the file into the config directory.

The qute://version page now also shows the uptime of qutebrowser.

qutebrowser now prompts to create a non-existing directory when starting a download.

:jseval --file now searches relative paths in a js/ subdir in qutebrowser’s data dir, e.g. ~/.local/share/qutebrowser/js.

The current/default bindings are now shown in the ``:bind` completion.

Empty categories are now hidden in the :open completion.

Search terms for URLs and titles can now be mixed when filtering the completion.

The default font size for the UI got bumped up from 8pt to 10pt.

Improved matching in the completion: The words entered are now matched in any order, and mixed matches on URL/tite are possible.

The system’s default encoding (rather than UTF-8) is now used to decode subprocess output.

qutebrowser now ensures it’s focused again after an external editor is closed.

The colors.completion.fg setting can now be a list, allowing to specify different colors for the three completion columns.

More consistent sizing for favicons with vertical tabs.

Using :home on pinned tabs is now prevented.

Fix crash with unknown file types loaded via qute://help.

Scrolling performance improvements.

Sites like qute://help now redirect to qute://help/ to make sure links work properly.

Fixes for the size calculation of pinned tabs in the tab bar.

Worked around a crash with PyQt 5.9.1 compiled against Qt < 5.9.1 when using :yank or qute:// URLs.

Fixed crash when opening qute://help/img.

Fixed gU (:navigate up) on qute://help and webservers not handling .. in a URL.

Using e.g. -s backend webkit to set the backend now works correctly.

Fixed crash when closing the tab an external editor was opened in.

When using :search-next before a search is finished, no warning about no results being found is shown anymore.

Fix :click-element with an ID containing non-alphanumeric characters.

Fix crash when a subprocess outputs data which is not decodable as UTF-8.

Fix crash when closing a tab immediately after hinting.

Worked around issues in Qt 5.10 with loading progress never being finished.

Fixed a crash when writing a flag before a command (e.g. `:-w open `).

Fixed a crash when clicking certain form elements with QtWebEngine.

:tab-detach has been deprecated, as :tab-give without argument can be used instead.

The long-deprecated :prompt-yes, :prompt-no, :paste-primary and :paste commands have been removed.

The invocation :download <url> <dest> which was deprecated in v0.5.0 was removed, use :download --dest <dest> <url> instead.

The messages.unfocused option which wasn’t used anymore was removed.

The x[xtb] default bindings got removed again as many users accidentally triggered them.

The qute://gpl page now works correctly again.

Trying to bind an empty command now doesn’t crash anymore.

Fixed crash when :config-write-py fails to write to the given path.

Fixed crash for some users when selecting a file with Qt 5.9.3

Improved handling for various SQL errors

Fix crash when setting content.cache.size to a big value (> 2 GB)

macOS and Windows builds are now built with PyQt 5.9.1 and Qt 5.9.2, including various bugfixes, as well as security fixes from Chromium up to version 61.0.3163.79.

Performance improvements for tab rendering.

The :open-editor command is now not hidden anymore as it’s also usable in normal mode.

Handle accessing a locked sqlite database gracefully

Abort pinned tab dialogs properly when a tab is closed e.g. by closing a window

Unbinding a default keybinding twice now doesn’t bind it again

Completions are now sorted correctly again when filtered

Fix workaround for black screens or crashes with Nvidia cards

Handle a filesystem going read-only gracefully

Fix crash when setting fonts.monospace

Fix list options not being modifiable via .append() in config.py

Mark the content.notifications setting as QtWebKit only correctly

Fix wrong rendering of keys like <back> in the completion

Nicer error messages and other minor improvements

Fixed starting after customizing fonts.tabs or fonts.debug_console.

Fixed starting with old PyQt versions compiled against newer Qt versions.

Fixed check for PyQt version to correctly enforce 5.7 (not 5.2).

Dependency changes:

The QtWebEngine backend is now used by default. Note this means that QtWebEngine now should be a required dependency, and QtWebKit (if new enough) should be changed to an optional dependency.

Completely rewritten configuration system which ignores the old config file. See qute://help/configuring.html for details.

Various documentation files got moved to the doc/ subfolder; qutebrowser.desktop got moved to misc/.

:set now doesn’t support toggling/cycling values anymore, that functionality got moved to :config-cycle.

New completion engine based on sqlite, which allows to complete the entire browsing history. The default for completion.web_history_max_items got changed to -1 (unlimited). If the completion is too slow on your machine, try setting it to a few 1000 items.

Up/Down now navigates through the command history instead of selecting completion items. Either use Tab to cycle through the completion, or restore the old behavior.

QtWebEngine: Spell checking support, see the spellcheck.languages setting.

New qt.args setting to pass additional arguments to Qt/Chromium.

New backend setting to select the backend to use. Together with the previous setting, this should make most wrapper scripts unnecessary.

qutebrowser can now be set as the default browser on macOS.

New config commands:

New :version command which opens qute://version.

New back/forward indicator in the statusbar.

New bindings.key_mappings setting to map keys to other keys.

QtWebEngine: Support for proxy authentication.

Using :download now uses the page’s title as filename.

Using :back or :forward with a count now skips intermediate pages.

When there are multiple messages shown, the timeout is increased.

:search now only clears the search if one was displayed before, so pressing <Escape> doesn’t un-focus inputs anymore.

Pinned tabs now adjust to their text’s width, so the tabs.width.pinned setting got removed.

:set-cmd-text now has a --run-on-count argument to run the underlying command directly if a count was given.

:scroll-perc got renamed to :scroll-to-perc.

Migrating QtWebEngine data written by versions before 2016-11-15 (before v0.9.0) is now not supported anymore.

Upgrading qutebrowser with a version older than v0.4.0 still running now won’t work properly anymore.

The --harfbuzz and --relaxed-config commandline arguments got dropped.

Exiting fullscreen via :fullscreen or buttons on a page now restores the correct previous window state (maximized/fullscreen).

When input.insert_mode.auto_load is set, background tabs now don’t enter insert mode anymore.

The keybinding help widget now works correctly when using keybindings with a count.

The window.hide_wayland_decoration setting now works correctly again.

Fixed empty space being shown after tabs in the tabbar in some cases.

Fixed :restart in private browsing mode.

Fixed printing on macOS.

Closing a pinned tab via mouse now also prompts for confirmation.

The "try again" button on error pages works correctly again.

:spawn -u -d is now disallowed.

:spawn -d shows error messages correctly now.

New dependency on PyQt5.QtOpenGL if QtWebEngine is used. QtWebEngine depends on QtOpenGL already, but on distributions packaging split PyQt5 wrappers, the wrappers for QtOpenGL are now required.

New dependency on PyOpenGL if QtWebEngine is used.

Private browsing is now implemented for QtWebEngine, and changed its behavior: The general -> private-browsing setting now only applies to newly opened windows, and you can use the -p flag to :open to open a private window.

New "pinned tabs" feature, with a new :tab-pin command (bound to <Ctrl-p> by default).

(QtWebEngine) Implemented :follow-selected.

New :clear-messages command to clear shown messages.

New ui -> keyhint-delay setting to configure the delay until the keyhint overlay pops up.

New -s option for :open to force a HTTPS scheme.

:debug-log-filter now accepts none as an argument to clear any log filters.

New --debug-flag argument which replaces --debug-exit and --pdb-postmortem.

New tabs -> favicon-scale option to scale up/down favicons.

colors -> statusbar.bg/fg.private and .command.private to customize statusbar colors for private windows.

New {private} field displaying [Private Mode] for ui -> window-title-format and tabs -> title-format.

(QtWebEngine) Proxy support with Qt 5.7.1 (already was supported for 5.8 and newer)

To prevent elaborate phishing attacks, the Punycode version (xn--*) is now shown in addition to the decoded version for international domain names (IDN).

Starting with legacy QtWebKit now shows a warning message. With the next release, support for it will be removed.

The Windows releases are redone from scratch, which means:

Improved qute://history page (with lazy loading)

Crash reports are not public anymore.

Paths like C: are now treated as absolute paths on Windows for downloads, and invalid paths are handled properly.

Comments in the config file are now placed before the individual options instead of being before sections.

Messages are now hidden when clicked.

stdin is now closed immediately for processes spawned from qutebrowser.

When ui -> message-timeout is set to 0, messages are now never cleared.

Middle/right-clicking the blank parts of the tab bar (when vertical) now closes the current tab.

The adblocker now also blocks non-GET requests (e.g. POST).

javascript: links can now be hinted.

:view-source, :tab-clone and :navigate --tab now don’t open the tab as "explicit" anymore, i.e. (with the default settings) open it next to the active tab.

qute:* pages now use qute://* instead (e.g. qute://version instead of qute:version), but the old versions are automatically redirected.

Texts in prompts are now selectable.

The default level for :messages is now info, not error

Trying to focus the currently focused tab with :tab-focus now focuses the last viewed tab.

(QtWebEngine) With Qt 5.9, content -> cookies-store can now be set without a restart.

(QtWebEngine) With Qt 5.9, better error messages are now shown for failed downloads.

(QtWebEngine) The underlying Chromium version is now shown in the version info.

(QtWebKit) Renderer process crashes now show an error page on Qt 5.9 or newer.

(QtWebKit) storage → offline-web-application-storage` got renamed to ...-cache

(QtWebKit) PAC now supports SOCKS5 as type.

The macOS .dmg is now built against Qt 5.9 which fixes various important issues (such as not being able to type dead keys).

Fixed crash with :download on PyQt 5.9.

Cloning a page without history doesn’t crash anymore.

When a download results in a HTTP error, it now shows the error correctly instead of crashing.

Pressing ctrl-c while a config error is shown works as intended now.

When the key config isn’t writable, we now show an error instead of crashing.

Fixed crash when unbinding an unbound key in the key config.

Fixed crash when using :debug-log-filter when --filter wasn’t given on startup.

Fixed crash with some invalid setting values.

Continuing a search after clearing it now works correctly.

The tabbar and completion should now be more consistently and correctly styled with various system styles.

Applying styles in qt5ct now shouldn’t crash anymore.

The validation for colors in stylesheets is now less strict, allowing for all valid Qt values.

data: URLs now aren’t added to the history anymore.

Accidentally starting with Python 2 now shows a proper error message again.

For some people, running some userscripts crashed - this should now be fixed.

Various other rare crashes should now be fixed.

The settings documentation was truncated with v0.10.1 which should now be fixed.

Scrolling to an anchor in a background tab now works correctly, and javascript gets the correct window size for background tabs.

(QtWebEngine) Added a workaround for a black screen with some setups

(QtWebEngine) Starting with Nouveau graphics now shows an error message instead of crashing in Qt.

(QtWebEngine) Retrying downloads now shows an error instead of crashing.

(QtWebEngine) Cloning a view-source tab now doesn’t crash anymore.

(QtWebEngine) window.navigator.userAgent is now set correctly when customizing the user agent.

(QtWebEngine) HTML fullscreen is now tracked for each tab separately, which means it’s not possible anymore to accidentally get stuck in fullscreen state by closing a tab with a fullscreen video.

(QtWebEngine) :scroll-page with --bottom-navigate now works correctly.

(QtWebKit) The HTTP cache is disabled on Qt 5.7.1 and 5.8 now as it leads to frequent crashes due to a Qt bug.

(QtWebKit) Fixed Crash when a PAC file returns an invalid value.

--qt-arg and --qt-flag can now also be used to pass arguments to Chromium when using QtWebEngine.

URLs are now redacted properly (username/password, and path/query for HTTPS) when using Proxy Autoconfig with QtWebKit

Crash when updating adblock lists with invalid UTF8-chars in them

Fixed the web inspector with QtWebEngine

Version checks when starting qutebrowser now also take the Qt version PyQt was compiled against into account

Hinting a input now doesn’t select existing text anymore with QtWebKit

The cursor now moves to the end when input elements are selected with QtWebEngine

Download suffixes like (1) are now correctly stripped with QtWebEngine

Crash when trying to print a tab which was closed in the meantime

Crash when trying to open a file twice on Windows

Userscripts now have a new $QUTE_COMMANDLINE_TEXT environment variable, containing the current commandline contents

New ripbang userscript to create a searchengine from a duckduckgo bang

QtWebKit Reloaded (also called QtWebKit-NG) is now fully supported

Various new functionality with the QtWebEngine backend:

New qute:history URL and :history command to show the browsing history

Open tabs are now auto-saved on each successful load and restored in case of a crash

:jseval now has a --file flag so you can pass a javascript file

:session-save now has a --only-active-window flag to only save the active window

macOS builds are back, and built with QtWebEngine

PyQt 5.7/Qt 5.7.1 is now required for the QtWebEngine backend

Scrolling with the scrollwheel while holding shift now scrolls sideways

New way of clicking hints which solves various small issues

When yanking a mailto: link via hints, the mailto: prefix is now stripped

Zoom level messages are now not stacked on top of each other anymore

qutebrowser now automatically uses QtWebEngine if QtWebKit is unavailable

:history-clear now asks for a confirmation, unless it’s run with --force.

input -> mouse-zoom-divider can now be 0 to disable zooming by mouse wheel

network -> proxy can also be set to pac+file://... now to use a local proxy autoconfig file (on QtWebKit)

(QtWebKit) Various rarely customized settings were removed:

Various bugs with Qt 5.8 and QtWebEngine:

Other QtWebEngine fixes:

:enter-mode now refuses to enter modes which can’t be entered manually (which caused crashes)

:record-macro (q) now doesn’t try to record macros for special keys without a text

Fixed PAC (proxy autoconfig) not working with QtWebKit

:download --mhtml now uses the new file dialog

Word hints are now upper-cased correctly when hints → uppercase is true

Font validation is now more permissive in the config, allowing e.g. "Terminus (TTF)" as font name

Fixed starting on newer PyQt/sip versions with LibreSSL

When downloading files with QtWebKit, a User-Agent header is set when possible

Fixed showing of keybindings in the :help completion

:navigate prev/next now detects rel attributes on <a> elements, and handles multiple rel attributes correctly

Fixed a crash when hinting with target userscript and spawning a non-existing script

Lines in Jupyter notebook now trigger insert mode

Prevent websites from downloading files to a location outside of the download folder with QtWebEngine.

New dependency: qutebrowser now depends on the Qt QML module, which is packaged separately in some distributions (as Qt Declarative/QML/Quick).

New :rl-backward-kill-word command which does what :rl-unix-word-rubout did before v0.8.0.

New :rl-unix-filename-rubout command which is similar to readline’s unix-filename-rubout.

New fonts -> completion.category setting to customize the font used for completion category headers.

New :debug-log-capacity command to adjust how many lines are logged into RAM (to report bugs which are difficult to reproduce).

New hide-unmatched-rapid-hints option to not hide hint unmatched hint labels in rapid mode.

New {clipboard} and {primary} replacements for the commandline which replace the :paste command.

New :insert-text command to insert a given text into a field on the page, which replaces :paste-primary together with the {primary} replacement.

New :window-only command to close all other windows.

New prev-category and next-category arguments to :completion-item-focus to focus the previous/next category in the completion (bound to <Ctrl-Tab> and <Ctrl-Shift-Tab> by default).

New :click-element command to fake a click on a element.

New :debug-log-filter command to change console log filtering on-the-fly.

New :debug-log-level command to change the console loglevel on-the-fly.

New general -> yank-ignored-url-parameters option to configure which URL parameters (like utm_source etc.) to strip off when yanking a URL.

Support for the HTML5 page visibility API

New readability userscript which shows a readable version of a page (using the readability-lxml python package)

New cast userscript to show a video on a Google Chromecast

New :run-with-count command which replaces the (undocumented) :count:command syntax.

New :record-macro (q) and :run-macro (@) commands for keyboard macros.

New ui -> hide-scrollbar setting to hide the scrollbar independently of the user-stylesheet setting.

New general -> default-open-dispatcher setting to configure what to open downloads with (instead of e.g. xdg-open on Linux).

Support for PAC (proxy autoconfig) with QtWebKit

Hints are now drawn natively in Qt instead of using web elements. This has a few implications for users:

:bookmark-add now has a --toggle flag which deletes the bookmark if it already exists.

:bookmark-load now has a --delete flag which deletes the bookmark after loading it.

:open now also accepts quickmark names instead of URLs

:tab-move now optionally takes an index for absolute moving.

Commands taking either an argument or a count (like :zoom or :tab-focus) now prefer the count instead of showing an error message.

:open now has an --implicit argument to treat the opened tab as implicit (i.e. to open it at the position it would be opened if it was a clicked link)

:download-open and :prompt-open-download now have an optional cmdline argument to pass a commandline to open the download with.

:yank now has a position argument to select what to yank instead of using flags.

Replacements like {url} can now also be used in the middle of an argument. Consequently, commands taking another command (:later, :repeat and :bind) now don’t immediately evaluate variables.

Tab titles in the :buffer completion now update correctly when a page’s title is changed via javascript.

:hint now has a --mode <mode> flag to override the hint mode configured using the hints -> mode setting.

With new-instance-open-target set to a tab option, the tab is now opened in the most recently focused (instead of the last opened) window. This can be configured with the new new-instance-open-target.window setting. It can also be set to last-visible to show the pages in the most recently visible window, or first-opened to use the first (oldest) available window.

Word hints now are more clever about getting the element text from some elements.

Completions for :help and :bind now also show hidden commands

The :buffer completion now also filters using the first column (id).

:undo has been improved to reopen tabs at the position they were closed.

:navigate now takes a count for up/increment/decrement.

The hints -> auto-follow setting now can be set to always/full-match/unique-match/never to more precisely control when hints should be followed automatically.

Counts can now be used with special keybindings (e.g. with modifiers). This was already implemented for v0.7.0 originally, but got reverted because it caused some issues and then never re-applied.

Sending a command to an existing instance (via "qutebrowser :reload") now doesn’t mark it as urgent anymore.

tabs -> title-format now treats an empty string as valid.

Bindings for :, / and ? are now configured explicitly and not hardcoded anymore.

The completion -> show setting can now be set to always, auto or never.

:open-editor can now be used in any mode.

Lots of improvements to and bugfixes for the QtWebEngine backend, such as working hints. However, using qutebrowser directly from git is still advised when using --backend webengine.

content -> javascript-can-open-windows got renamed to javascript-can-open-windows-automatically.

:prompt-accept now optionally accepts a value which overrides the one entered in the input box. yes and no can be used as values for yes/no questions.

The new --qt-arg and --qt-flag arguments can be used to pass arguments/flags to Qt’s commandline.

Error/warning/info messages are now shown stacked above the statusbar. This also added various new settings:

The qute:settings page now also shows option descriptions.

qute:version and qutebrowser --version now show various important paths

:spawn/userscripts now show a nicer error when a script wasn’t found

Various functionality now works when javascript is disabled with QtWebKit

Various commands/settings taking left/right/previous arguments now take prev/next/last-used to remove ambiguity.

The ui -> user-stylesheet setting now only takes filenames, not CSS snippets

ui -> window-title-format now has a new `xhtml11 ` replacement

:hint has a new --add-history argument to add the URL to the history for yank/spawn targets.

:set now cycles through values if more than one argument is given.

:open now opens default-page without a URL even without -t/-b/-w given.

The :paste command got deprecated as :open with {clipboard} and {primary} can be used instead.

The :paste-primary command got deprecated as :insert-text {primary} can be used instead.

The :prompt-yes and :prompt-no commands got deprecated as :prompt-accept yes and :prompt-accept no can be used instead.

The :yank-selected command got merged into :yank as :yank selection and thus removed.

The :completion-item-prev and :completion-item-next commands got merged into a new :completion-focus {prev,next} command and thus removed.

The ui -> hide-mouse-cursor setting since it was completely broken and nobody seemed to care.

The hints -> opacity setting - see the "Changed" section for details.

The completion -> auto-open setting got merged into completion -> show and thus removed.

All --qt-* arguments got replaced by --qt-arg and --qt-flag and thus removed.

The -c/--confdir, --datadir and --cachedir arguments got removed, as --basedir should be sufficient.

:undo now doesn’t undo tabs "closed" by :tab-detach anymore.

Fixed an issue with hint chars not being cleared correctly when leaving hint mode.

:tab-detach now fails correctly when there’s only one tab open.

Various small issues with the command completion

Fixed hang when using multiple spaces in a row with the URL completion

qutebrowser now still starts with an incorrectly configured $XDG_RUNTIME_DIR.

Fixed crash when a userscript writes invalid unicode data to the FIFO

Fixed crash when a included HTML was not found

Fixed crash when doing :<space><enter>, another corner-case introduced in v0.8.0

Fixed :open-editor (<Ctrl-e>) on Windows

Fixed crash when setting general -> auto-save-interval to a too big value.

Fixed crash when using hints on Void Linux.

Fixed compatibility with Python 3.5.2+ on Debian unstable

Compatibility with pdfjs v1.6.210

:bind can now be used to bind to an alias (binding by editing keys.conf already worked before)

The command completion now updates correctly when changing aliases

The tabbar now displays correctly with the Adwaita Qt theme

The default sk keybinding now sets the commandline to :bind correctly

Fixed crash when closing a window without focusing it

Userscripts now can access QUTE_FIFO correctly on Windows

Fixed general -> private-browsing not being set correctly until a restart (which caused e.g. local storage to be enabled).

When hinting input fields (:t), also consider input elements without a type.

Fixed crash when opening an invalid URL with a percent-encoded and a real @ in it

Fixed default ;o and ;O bindings

Fixed local storage not working (and possible other bugs) when using a relative path with --basedir.

Fixed crash when deleting a quickmark with Ctrl-D

Fixed HTML5 video playback on Windows

Fixed crash when using ‘:prompt-open-download` with a file with chars not encodable with the OS’ filesystem encoding (e.g. with LC_ALL=C)

Fixed :prompt-open-download with a too long filename (> 255 bytes)

Fixed crash when cancelling a download after doing :prompt-open-download

Fixed crash when writing a download to disk fails with :prompt-open-download.

Fixed :restart deleting the basedir when it was given with --basedir.

Fix crash when pressing enter without a command

Adjust error message to point out QtWebEngine is unsupported with the OS X .app currently.

Hide Harfbuzz warning with the macOS .app

New :repeat-command command (mapped to .) to repeat the last command. Note that two former default bundings conflict with that binding, unbinding them via :unbind .i and :unbind .o is recommended.

New qute:bookmarks page which displays all bookmarks and quickmarks.

New :prompt-open-download (bound to Ctrl-X) which can be used to open a download directly when getting the filename prompt.

New {host} replacement for tab- and window titles which evaluates to the current host.

New default binding ;t for :hint input.

New variables $QUTE_CONFIG_DIR, $QUTE_DATA_DIR and $QUTE_DOWNLOAD_DIR available for userscripts.

New option ui → status-position to configure the position of the status bar (top/bottom).

New --pdf <filename> argument for :print WHICH can be used to generate a PDF without a dialog.

:scroll-perc now prefers a count over the argument given to it, which means gg can be used with a count.

Aliases can now use ;; to have an alias which executed multiple commands.

:edit-url now does nothing if the URL isn’t changed in the spawned editor.

:bookmark-add can now be passed a URL and title to add that as a bookmark rather than the current page.

New taskadd userscript to add a taskwarrior task annotated with the current URL.

:bookmark-del and :quickmark-del now delete the current page’s URL if none is given.

Compatibility with PyQt 5.7

Fixed some configuration values being lost when a config option gets removed from qutebrowser’s code.

Fix crash when downloading with a full disk

Using :jump-mark (e.g. '') when the current URL is invalid doesn’t crash anymore.

The ability to display status messages from webpages, as well as the related ui -> display-statusbar-messages setting.

The general -> wrap-search setting as searches now always wrap. According to a quick straw poll and prior crash logs, almost nobody is using wrap-search = false, and turning off wrapping is not possible with QtWebEngine.

:edit-url now doesn’t accept a count anymore as its behavior was confusing and it doesn’t make much sense to add a count.

New :edit-url command to edit the URL in an external editor.

New network -> custom-headers setting to send custom headers with every request.

New {url:pretty} commandline replacement which gets replaced by the decoded URL.

New marks to remember a scroll position:

New :jump-mark command to jump to a mark, bound to '

New :set-mark command to set a mark, bound to ```(backtick)

The ' mark gets set when moving away (hinting link with anchor, searching, etc.) so you can move back with ''

New --force-color argument to force colored logging even if stdout is not a terminal

New :messages command to show error messages

New pop-up showing possible keybinding when the first key of a keychain is pressed. This can be turned off using :set ui keyhint-blacklist *.

New hints -> auto-follow-timeout setting to ignore keypresses after following a hint when filtering in number mode.

New :history-clear command to clear the entire history

New hints -> find-implementation to select which implementation (JS/Python) should be used to find hints on a page. The javascript implementation is better, but slower.

New inputs group for :hint to hint text input fields.

qutebrowser got a new (slightly updated) logo

:tab-focus can now take a negative index to focus the nth tab counted from the right.

:yank can now yank the pretty/decoded URL by adding --pretty

:navigate now clears the URL fragment

:completion-item-del (Ctrl-D) can now be used in :buffer completion to close a tab

Various SSL ciphers are now disabled by default. With recent Qt/OpenSSL versions those already all are disabled, but with older versions they might not be.

Show favicons as window icon with tabs-are-windows set.

:bind <key> without a command now shows the existing binding

The optional colorlog dependency got removed, as qutebrowser now displays colored logs without it.

URLs are now shown decoded when hovering.

Keybindings are now shown in the command completion

Improved behavior when pasting multiple lines

Rapid hints can now also be used for the normal hint target, which can be useful with javascript click handlers or checkboxes which don’t actually open a new page.

:zoom-in or :zoom-out (+/-) with a too large count now zooms to the smallest/largest zoom instead of doing nothing.

The commandline now accepts partially typed commands if they’re unique.

Number hints are now kept filtered after following a hint in rapid mode.

Number hints are now renumbered after filtering

Number hints can now be filtered with multiple space-separated search terms

hints -> scatter is now ignored for number hints

Better history implementation which also stores titles. As a consequence, URLs which redirect to another URL are now added to the history too, marked with a -r suffix to the timestamp field.

Fixed using :hint links spawn with flags - you can now use things like the -v argument for :spawn or pass flags to the spawned commands.

Various fixes for hinting corner-cases where following a link didn’t work or the hint was drawn at the wrong position.

Fixed crash when downloading from a URL with SSL errors

Close file handles correctly when a download failed

Fixed crash when using ;Y (:hint links yank-primary) on a system without primary selection

Don’t display quit confirmation with finished downloads

Fixed updating the tab index in the statusbar when opening a background tab

Fixed a crash when entering `:-- ` in the commandline

Fixed :debug-console with PyQt 5.6

Fixed qutebrowser not starting when sys.stderr is None

Fixed crash when cancelling a download which belongs to an MHTML download

Fixed rebinding of keybindings being case-sensitive

Fix for tab indicators getting lost when moving tabs

Fixed handling of backspace in number hinting mode

Fixed FileNotFoundError when starting in some cases on old Qt versions

Fixed sharing of cookies between tabs when private-browsing is enabled

Toggling values with :set now uses lower-case values

Hints now work with (non-standard) links with spaces around the URL

Strip off trailing spaces for history entries with no title

Fixed crash when using :tab-{prev,next,focus} right after closing the last tab with last-close set to close.

Fixed crash when doing :undo in a new instance with tabs -> last-close set to default-page.

Fixed crash when starting with --cachedir=""

Fixed crash in some circumstances when using dictionary hints

Fixed various crashes related to PyQt 5.6

Fixed broken cheatsheet image which was missing from package

Fixed occasional crash when switching/disconnecting monitors

Fixed crash when downloading non-ascii files with a broken locale (LC_ALL=C)

Added workaround for a Qt/PyQt bug which is too weird to describe here

New :buffer command to easily switch tabs by name. This is not bound to a key by default for existing users due to a conflict with the gt/gT bindings (which are now removed from the default bindings). You can bind it by hand by running :bind -f gt set-cmd-text -s :buffer.

New --quiet argument for the :debug-pyeval command to not open a tab with the results. Note :debug-pyeval is still only intended for debugging.

The completion now matches each entered word separately.

A new command :paste-primary got added to paste the primary selection, and <Shift-Insert> got added as a binding so it pastes primary rather than clipboard.

New mode word for hints -> mode which uses a dictionary and link-texts for hints instead of single characters.

New --all argument for :download-cancel to cancel all running downloads.

New password_fill userscript to fill passwords using the pass executable.

New current hinting mode which forces opening hints in the current tab (even with target="_blank")

Pasting multiple lines via :paste now opens each line in a new tab.

:navigate increment/decrement now preserves leading zeroes in URLs.

general -> editor can now also handle {} inside another argument (e.g. to open vim via termite)

Improved performance when scrolling with many tabs open.

Shift-Insert now also pastes primary selection for prompts.

:download-remove --all got un-deprecated to provide symmetry with :download-cancel --all. It does the same as :download-clear.

Improved detection of URLs/search terms when pasting multiple lines.

Don’t remove qutebrowser-editor-* temporary file if editor subprocess crashed

Userscripts are also searched in /usr/share/qutebrowser/userscripts.

Blocked hosts are now also read from a blocked-hosts file in the config dir (e.g. ~/.config/qutebrowser/blocked-hosts).

Fixed starting with -c "".

Fixed crash when a tab is closed twice via javascript (e.g. Dropbox authentication dialogs)

Fixed crash when a notification/geolocation prompt is answered after closing the tab it belongs to.

Fixed crash when downloading a file without any path information (e.g a magnet link).

Fixed crashes when opening an empty URL (e.g. via pasting).

Fixed validation of duplicate values in hints -> chars.

Fixed crash when PDF.js was partially installed.

Fixed crash when XDG_DOWNLOAD_DIR was not an absolute path.

Fixed very long filenames when downloading data://-URLs.

Fixed ugly UI fonts on Windows when Liberation Mono is installed

Fixed crash when unbinding key from a section which doesn’t exist in the config

Fixed report window after a segfault

Fixed some directory browser issues on Windows

Fixed crash when closing a window with a finished download and delayed remove-finished-downloads setting.

Fixed crash when hitting <Tab> then <Ctrl-C> on pages without keyboard focus.

Fixed "Frame load interrupted by policy change" error showing up when downloading files with Qt 5.6.

The gt/gT bindings (luakit-like alternatives to J/K) were removed (except for existing configs) to make room for the gt binding to show buffers.

Fixed completion for various config values when using :set.

Fixed config validation for various config values.

Prevented an error being logged when a website with HTTP authentication was opened on Windows.

Ability to preview PDFs using pdf.js in the browser if it’s installed. This is disabled by default and can be enabled using the content -> pdfjs-enabled setting.

New setting ui -> hide-wayland-decoration to hide the window decoration when using wayland.

New userscripts in misc/userscripts:

open_download to easily open a file in your downloads folder.

view_in_mpv to open a video in mpv and remove it from the page.

qutedmenu and dmenu_qutebrowser to select URLs via dmenu

New setting content -> host-blocking-whitelist to whitelist certain domains from the adblocker.

{scroll_pos} can now be used in ui -> window-title-format and tabs -> title-format.

New setting general -> url-incdec-segments to configure which segments of the URL should be affected by :navigate increment/decrement.

New --target argument to specify how URLs should be opened in an existing instance.

New setting statusbar.url.fg.success.https to set the foreground color for the URL when a page was loaded via HTTPS.

The scrollbar in the completion is now styled, and the following new options got added:

New value none for options taking a color system so they don’t display a gradient:

New command :download-retry to retry a failed download.

New command :download-clear which replaces :download-remove --all.

:set-cmd-text has a new --append argument to append to the current statusbar text.

qutebrowser now uses ~/.netrc if available to authenticate via HTTP.

New :fake-key command to send a fake keypress to a website or to qutebrowser.

New --mhtml argument for :download to download a page including all resources as MHTML file.

New option tabs -> title-alignment to change the alignment of tab titles.

The colors -> tabs.bg/fg.selected option got split into tabs.bg/fg.selected.odd/even.

:spawn --userscript and :hint with the userscript target now look up relative paths in ~/.local/share/qutebrowser/userscripts or $XDG_DATA_HOME. Using a binary in $PATH won’t work anymore with --userscript.

New design for error pages

Link filtering for hints now checks if the text is contained anywhere in the link, and matches case-insensitively.

The ui -> remove-finished-downloads option got changed to an integer and now takes a time (in milliseconds) to keep the download around after it’s finished. When set to -1, downloads are never removed.

The :follow-hint command now optionally takes the keystring of a hint to follow.

:scroll-px now doesn’t take floats anymore, which made little sense.

Updated the user agent list for the :set network user-agent completion.

Starting with --debug doesn’t log VDEBUG messages anymore (add --loglevel VDEBUG to get them).

:debug-console now hides the console if it’s already shown.

:yank-selected now doesn’t log the selected text anymore.

general -> log-javascript-console got changed from a boolean to an option taking a loglevel (none, info, debug).

:tab-move +/- now wraps around if tabs -> wrap is true.

When a subprocess (like launched by :spawn) fails, its stdout/stderr is now logged to the console.

A search engine name can now contain any non-space character, like dashes.

:download-remove --all is now deprecated and :download-clear should be used instead.

:download <url> <destination> is now deprecated and :download --dest <destination> <url> should be used instead.

:scroll with two pixel-arguments (deprecated in v0.3.0)

The :run-userscript command (deprecated in v0.2.0)

The rapid and rapid-win targets for :hint (deprecated in v0.2.0)

The :cancel-download command (deprecated in v0.2.0)

The :download-page command (deprecated in v0.2.0)

Fixed retrying of downloads which were started in a now closed tab.

Fixed displaying of web history if web-history-max-items is set to -1.

Cloned tabs now don’t display favicons anymore if show-favicons is False.

Fixed a crash when clicking a bookmark name and pressing Ctrl-D.

Fixed a crash when a website presents a very small favicon.

Fixed prompting for download directory when storage -> prompt-download-directory was unset.

Fixed crash when using :follow-hint outside of hint mode.

Fixed crash when using :set foo bar? with invalid section/option.

Fixed scrolling to the very left/right with :scroll-perc.

Using an external editor should now work correctly with some funny chars (U+2028/U+2029/BOM).

Movements in caret mode now should work correctly on macOS and Windows.

Fixed upgrade from earlier config versions.

Fixed crash when killing a running userscript.

Fixed characters being passed through when shifted with forward-unbound-keys set to auto.

Fixed restarting after a crash is reported.

Removed .pyc files accidentally contained in source releases.

Adjusted AppArmor config for the IPC changes in v0.4.0.

Fixed atime update frequency for IPC file.

Worked around a Qt issue where middle-clicking caused scrolling with a touchpad to restart at the beginning of the page.

The completion -> web-history-max-items setting is now also respected for items added after starting qutebrowser.

Search terms are now shared between different tabs again

Tests (a reduced subset of them) now run correctly again when DISPLAY is not set.

Fixed an issue causing qutebrowser to crash with Python 3.5 as soon as an ad was blocked.

Fixed an issue causing qutebrowser to not start with more recent Python 3.4 versions (e.g. on Debian experimental).

Fixed various PendingDeprecationWarnings shown with Python 3.5.

New bookmark functionality (similar to quickmarks without a name).

New (hidden) command :completion-item-del (bound to <Ctrl-D>) to delete the current item in the completion (for quickmarks/bookmarks).

New settings tabs -> padding and tabs -> indicator-tabbing to control the size/padding of the tabbar.

New setting ui -> statusbar-padding to control the size/padding of the status bar.

New setting network -> referer-header to configure when the referer should be sent (by default it’s only sent while on the same domain).

New setting tabs -> show which supersedes the old tabs -> hide-* options and has an additional switching option which shows tab while switching them. There’s also a new show-switching option to configure the timeout.

New setting storage -> remember-download-directory to remember the last used download directory.

New setting storage -> prompt-download-directory to download all downloads without asking.

Rapid hinting is now also possible for downloads.

Directory browsing via file:// is now supported.

Some developer scripts got moved to scripts/dev/

When downloading to a FIFO or special file, a confirmation is displayed as this might cause qutebrowser to hang.

The :yank-selected command now works in all modes instead of just caret mode and is not hidden anymore.

minimal_webkit_testbrowser.py now has a --webengine switch to test QtWebEngine if it’s installed.

The column width percentages for the completion view now depend on the completion model.

The values for tabs -> position and ui -> downloads-position got changed from north/south/west/`east to top/bottom/left/right. Existing configs should be adjusted automatically.

:tab-focus/gt now behaves like :tab-next if no count/index is given.

The completion widget doesn’t show a border anymore.

The tabbar doesn’t display ugly arrows anymore if there isn’t enough space for all tabs.

Some insignificant Qt warnings which were printed on macOS are now hidden.

Better support for Qt 5.5 and Python 3.5.

Fixed a bug where cookies were saved despite qutebrowser being started in private browsing mode.

The local socket used for inter-process communication (opening new instances) is now ensured to only be accessible by the user on all operating systems.

Various corner cases for inter-process communication issues got fixed.

link_pyqt.py now should work better on untested distributions.

Fixed various corner-cases with crashes when reading invalid config values and the history file.

Fixed various corner-cases when setting text via an external editor.

Fixed potential crash when hinting a text field.

Fixed entering of insert mode when certain disabled text fields were clicked.

Fixed a crash when using :set with -p and ! (invert value)

Downloads with unknown size are now handled correctly.

:navigate increment/decrement (<Ctrl-A>/<Ctrl-X>) now handles some corner-cases better.

Fixed a bug where the completion got affected by another window’s completion if it was open in both windows.

Fixed a performance issue with large histories when opening previously unvisited websites.

The progress bar now doesn’t cause the statusbar to change it’s height anymore.

~ is now always expanded when spawning a script.

Fixed various corner cases when opening links in an existing instance.

Fixed a race-condition causing an exception when starting qutebrowser.

The tabs -> indicator-space setting got removed as the new padding settings should be used instead.

The tabs -> hide-always and tabs -> hide-auto settings got merged into the new tabs -> show setting.

New commands :message-info, :message-error and :message-warning to show messages in the statusbar, e.g. from a userscript.

New command :scroll-px which replaces :scroll for pixel-exact scrolling.

New command :jseval to run a javascript snippet on the current page.

New (hidden) command :follow-selected (bound to Enter/Ctrl-Enter by default) to follow the link which is currently selected (e.g. after searching via /).

New (hidden) command :clear-keychain to clear a partially entered keychain (bound to <Escape> by default, in addition to clearing search).

New setting ui -> smooth-scrolling.

New setting content -> webgl to enable/disable WebGL.

New setting content -> css-regions to enable/disable support for CSS Regions.

New setting content -> hyperlink-auditing to enable/disable support for hyperlink auditing.

New setting tabs -> mousewheel-tab-switching to control mousewheel behavior on the tab bar.

New arguments --datadir and --cachedir to set the data/cache location.

New arguments --basedir and --temp-basedir (intended for debugging) to set a different base directory for all data, which allows multiple invocations.

New argument --no-err-windows to suppress all error windows.

New arguments --top-navigate and --bottom-navigate (-t/-b) for :scroll-page to specify a navigation action (e.g. automatically go to the next page when arriving at the bottom).

New flag -d/--detach for :spawn to detach the spawned process so it’s not closed when qutebrowser is.

New flag -v/--verbose for :spawn to print information when the process started/exited successfully.

Many new color settings (foreground setting for every background setting).

New setting ui -> modal-js-dialog to use the standard modal dialogs for javascript questions instead of using the statusbar.

New setting colors -> webpage.bg to set the background color to use for websites which don’t set one.

New setting completion -> auto-open to only open the completion when tab is pressed (if set to false).

New visual/caret mode (bound to v) to select text by keyboard.

There are now some example userscripts in misc/userscripts.

Support for Qt 5.5 and tox 2.0

Breaking change for userscripts: QUTE_HTML and QUTE_TEXT for userscripts now don’t store the contents directly, and instead contain a filename.

The content -> geolocation and notifications settings now support a true value to always allow those. However, this is not recommended.

New bindings <Ctrl-R> (rapid), <Ctrl-F> (foreground) and <Ctrl-B> (background) to switch hint modes while hinting.

<Ctrl-M> and numpad-enter are now bound by default for bindings where <Return> was bound.

:hint tab and F now respect the background-tabs setting. To enforce a foreground tab (what F did before), use :hint tab-fg or ;f.

:scroll now takes a direction argument (up/down/left/right/top/bottom/page-up/page-down) instead of two pixel arguments (dx/dy). The old form still works but is deprecated.

The ui -> user-stylesheet setting now also takes file paths relative to the config directory.

The content -> cookies-accept setting now has new no-3rdparty (default) and no-unknown-3rdparty values to block third-party cookies. The default value got renamed to all.

Improved startup time by reading the webpage history while qutebrowser is open.

The way :spawn splits its commandline has been changed slightly to allow commands with flags.

The default for the new-instance-open-target setting has been changed to tab.

Sessions now store zoom/scroll-position separately for each entry.

:scroll with two pixel-arguments is now deprecated - :scroll-px should be used instead.

The --no-crash-dialog argument which was intended for debugging only was removed as it’s replaced by --no-err-windows which suppresses all error windows.

Support for Qt installations without SSL support was dropped.

Scrolling should now work more reliably on some pages where arrow keys worked but hjkl didn’t.

Small improvements when checking if an input is a URL or not.

Fixed wrong cursor position when completing the first item in the completion.

Fixed a bug where the same title was shown for all tabs on some systems.

Don’t install the scripts package when installing qutebrowser.

Fixed searching for terms starting with a hyphen (e.g. /-foo)

Proxy authentication credentials are now remembered between different tabs.

Fixed updating of the tab title on pages without title.

Fixed AssertionError when closing many windows quickly.

Various fixes for deprecated key bindings and auto-migrations.

Workaround for qutebrowser not starting when there are NUL-bytes in the history (because of a currently unknown bug).

Fixed handling of keybindings containing Ctrl/Meta on macOS.

Fixed crash when downloading a URL without filename (e.g. magnet links) via "Save as…".

Fixed exception when starting qutebrowser with :set as argument.

Fixed horrible completion performance when the shrink option was set.

Sessions now store zoom/scroll-position correctly.

Added missing manpage (doc/qutebrowser.1.asciidoc) to archive.

Session support

New commands to manage downloads:

History completion

Better save logic for the config/state:

Opera-like mouse rocker gestures

New -f option for :reload to reload and bypass the cache.

Pass more information (QUTE_MODE, QUTE_SELECTED_TEXT, QUTE_SELECTED_HTML, QUTE_USER_AGENT, QUTE_HTML, QUTE_TEXT) to userscripts.

New --userscript option to :spawn (which deprecates :run-userscript).

Ability to toggle a value to :set by appending a ! to the value.

New options to hide the tab-/statusbar:

New options to configure how the tab/window titles should look:

HTML5 Geolocation/Notification support:

New options to disable javascript prompts/alerts:

Two new options to customize the behavior of hints:

Make it possible to use :open -[twb] without url.

New input -> partial-timeout option to clear partial keystrings.

New option completion -> download-path-suggestion to configure what to show in the completion for downloads.

Queue messages shown in unfocused windows and show them when the window is focused.

New --relaxed-config argument which ignores unknown options.

New :tab-detach command to open the current tab in a new window.

Zooming via Ctrl-Mousewheel.

New option (content -> host-blocking-enabled) to enable/disable host blocking.

New values tab-bg/tab-bg-silent for new-instance-open-target to open a background tab.

New ui -> downloads-position setting to move the downloads to the bottom.

New ui -> hide-mouse-cursor option to hide the mouse cursor inside qutebrowser.

New argument -s for qutebrowser to set a temporary config option.

New argument -p for the :set command to print the new value.

New --rapid option to :hint. The rapid/rapid-win targets are now deprecated, and --rapid can be used as well with the targets run/hover/userscript/spawn as well.

New -f argument to :bind to overwrite the old binding.

New --qt-name argument to qutebrowser which is passed to Qt to set WM_CLASS.

Alternating row colors in completion. This adds a new colors -> completion.alternate-bg option.

Ignore quotes with maxsplit-commands (:open, :quickmark-load, etc.) and don’t quote arguments for those commands in the completions. This also means some commands needed adjustments:

Ignore ;; for splitting with some commands like :bind.

Add unbound (new) default keybindings to config. This also adds a new <unbound> special command.

If an SSL error is raised multiple times with the same error/certificate/host/scheme/port, the user is only asked once.

Jump to last instead of first item when pressing Shift-Tab the first time in the completion.

Add a fullscreen keybinding.

Add a :search command in addition to /foo so it’s more visible and can be used from scripts.

Various improvements to documentation, logging, and the crash reporter.

Expand ~ to the users home directory with :run-userscript.

Improve the userscript runner on Linux/macOS by using QSocketNotifier.

Add luakit-like gt/gT keybindings to cycle through tabs.

Show default value for config values in the completion.

Clone tab icon, tab text and zoom level when cloning tabs.

Don’t open relative file paths with :open, only with commandline arguments.

Expand environment variables in config settings which take a file path.

Add a list of common user agents to the user agent setting completion.

Move cursor to end of textboxes when hinting.

Don’t start searches on invalid URLs for quickmarks/startpage.

Various performance improvements for the completion.

Always open URLs given as argument in the foreground.

Improve various error messages.

Add startpage/default-page values to tabs -> last-close.

Various improvements to :restart - it should be more robust now and uses sessions so all state (focused tab, scroll position, etc.) gets remembered.

Add tab index display to the statusbar.

Keep progress bar height fixed when the statusbar is multiline.

Many improvements to tests and related infrastructure:

The :run-userscript command - use :spawn --userscript instead.

The rapid and rapid-win targets for :hint - use the --rapid argument to :hint instead.

The :cancel-download command - use :download-cancel instead.

The :download-page command - use :download instead.

init_venv.py and run_checks.py have been replaced by tox. Install tox and run tox -e mkvenv instead..

Fix for cache never being used.

Fixed handling of key release events (e.g. for javascript) when holding a key and pressing a second one.

Fix handling of commands using ;; at various places (key config, command parser, :bind)

Fix splitting of flags with arguments (:bind -m/--mode).

Fix bindings of special keys with lower-case modifiers (e.g. <ctrl-x>)

Fix for weird search highlights when changing tabs while search is active.

Fix starting with -c "".

Fix removing of partial downloads when a download is cancelled via context menu.

Fix retrying of downloads which were started in a now closed tab.