qutebrowser: download ældre versioner

Added
- New :quickmark-reload and :bookmark-reload commands to reload quick-/bookmarks from disk (#8845).
Changed
- Windows and macOS releases now ship with Qt 6.11.0, which is based on Chromium 140.0.7339.225 with security patches up to 146.0.7680.80.
Deprecated
- Support for Python 3.9 is not tested anymore, and will be fully removed in the next release (#8731).
Fixed
- Added a workaround for graphic/flickering issues with Qt 6.11.0, AMD graphics and Wayland (#8908).
- Compatibility with PDF.js >= 5.5.207 (#8885).
- datalist dropdowns not opening correctly on Wayland/Sway (#8831). This was caused by an old workaround for a different QtWebEngine issue, which is now disabled for QtWebEngine 6.6.3 and newer.
- The workaround avoiding Google blocking sign ins from qutebrowser was updated, although it’s unclear if this will fix the issue as the behavior is wildly inconsistent.
- Added a workaround for QtWebEngine 6.11 crashing on Google Mail / Meet (#8914).
- The workaround avoiding crashes with Qt 6.10.1 and qt.workarounds.disable_hangouts_extension (or --version) has now been extended to Qt 6.10.2 as well (#8785, #8841).
- ANSI color codes now don’t end up in commands.asciidoc anymore when regenerating it using Python 3.14.
- The GenericName in the .desktop file is now correct for Ukrainian and Chinese (#8836).

Fixed
- New qt.workarounds.disable_accessibility setting, which disables Chromium accessibility support. By default, is it set to auto, which only disables accessibility on Qt versions with known issues. This works around a bug in Qt 6.10.1 causing frequent segfaults (#8797).

Changed
- Windows and macOS releases now ship with Qt 6.10.1, which include security patches up to Chromium 142.0.7444.162.
Fixed
- The version info now includes the Wayland compositor name if wayland-client is available under a different name than libwayland-client.so (#8771).
- The list of Chromium extensions in --version / :version now uses the correct Chromium data profile, also fixing a crash with Qt 6.10.1 (#8785).
- With Qt 6.10.1, qt.workarounds.disable_hangouts_extension now doesn’t apply on private profiles, avoiding a Qt bug leading to a crash (#8785).

Fixed
- A regression in v3.6.0 where the page didn’t have keyboard focus after closing the completion, so e.g. typing in an input field after hinting didn’t work. (#8750)

Added
- The :version info now shows additional information:
- The X11 window manager / Wayland compositor name (mostly useful for bug/crash reports).
- Loaded WebExtensions (partial support landed in QtWebEngine 6.10, no official qutebrowser support yet).
- Support for hinting elements which are part of an (open) shadow DOM.
Changed
- The qutedmenu userscript now sorts history by the last access time.
- Hardware accelerated 2D canvas is now enabled by default on Qt 6.8.2+, as graphic glitches with e.g. PDF.js and Google Sheets should be fixed nowadays. If you still run into issues, please report them and set qt.workarounds.disable_accelerated_2d_canvas to always to disable it again.
- Changes to binary releases:
- Windows and macOS releases are now built with Qt 6.10.0, which is based on Chromium 134.0.6998.208 with security patches up to 140.0.7339.207.
- Windows and macOS releases are now built with Python 3.14.
- Windows releases are now built on Windows Server 2022 (previously 2019), which might break compatibility with older Windows releases (untested).
- If using mkvenv.py on Linux, note that Qt now requires glibc v2.34 (v2.28 previously). This is available down to Ubuntu 22.04 LTS and Debian Bookworm (oldstable), so this should not affect most users of desktop distributions.
Fixed
- Fixed crash if two new downloads start while a download prompt is already open (#8674).
- Fixed exception when closing a qutebrowser window while a download prompt is still open.
- Hopefully proper fix for some web pages jumping to the top when the statusbar is hidden (#8223).
- Fix for the page header being shown on YouTube after the fullscreen notification was hidden (#8625).
- Fix for videos losing keyboard focus when the fullscreen notification shows (#8174).
- The workaround for microphone/camera permissions not being requested with QtWebEngine 6.9 on Google Meet, Zoom, or other pages using the new <permission> element now got extended to Qt 6.9.1+ as it’s still not fixed upstream. (#8612)
- The package version for Jinja 3.3+ is now correctly displayed in :version.
- Fixed crash with Qt 6.10 (and possibly older Qt versions) when navigating from a qute:// page to a web page, e.g. when searching on qute://start.
- On Wayland with Qt ⇐ 6.9, EGL_PLATFORM=wayland is now set by qutebrowser to get hardware rendering. Qt 6.10 includes an equivalent fix (#8637).
- Added workaround for per-domain User-Agent header not being used on redirects (#8679).
- Added site-specific quirk for gitlab.gnome.org agressively blocking old Chromium versions (and thus QtWebEngine) (#8509).
- Using :config-list-remove with an invalid value for the respective option type now corrently displays an error instead of crashing.

Deprecated
- QtWebKit (legacy) support got removed from CI and is now untested. If it breaks, it’s not going to be fixed, and support will be removed over the next releases.
- Qt 5 support is currently still tested, but is also planned to get removed over the next releases. Same goes for support for older Qt 6 versions (likely 6.2/6.3/6.4 and perhaps 6.5, see #8464).
Changed
- Windows/macOS releases now bundle Qt 6.9.1, including many graphics-related bugfixes, as well as security patches up to Chromium 136.0.7103.114.
Fixed
- A bogus "wildcard call disconnects from destroyed signal" warning from Qt is now suppressed.
- PDF.js now loads correctly on Windows installations with broken mimetype configurations.
- A "Ignoring new child …" debug log message which got spammy with Qt 6.9 is now removed.
- A unknown crash (possibly related to using devtools) due to weird (Py)Qt behavior now has a workaround.
- No "QtWebEngine version mismatch" warning is now logged anymore with newer Qt 5.15 releases (but you should still stop using Qt 5).
- The PDF.js version can now correctly be extracted/displayed with newer PDF.js versions.
- The qute-bitwarden, -lastpass and -pass userscripts now properly avoid a DeprecationWarning from the upcoming 6.0 release of tldextract. The previous fix in v3.5.1 was insufficient.

Changed
- Windows/macOS releases are now built with Qt 6.9.0
- Based on Chromium 130.0.6723.192
- Security fixes up to Chromium 133.0.6943.141
- The content.headers.user_agent setting now has a new {upstream_browser_version_short} template field, which is the upstream/Chromium version but shortened to only major version.
- The default user agent now uses the shortened Chromium version and doesn’t expose the QtWebEngine/... part anymore, thus making it equal to the corresponding Chromium user agent. This increases compatibilty due to various overzealous "security" products used by a variety of websites that block QtWebEngine, presumably as a bot (known issues existed with Whatsapp Web, UPS, Digitec Galaxus).
- Changed features in userscripts:
- qute-bitwarden now passes your password to the subprocess in an environment variable when unlocking your vault, instead of as a command line argument. (#7781)
- New -D no-system-pdfjs debug flag to ignore system-wide PDF.js installations for testing.
- Polyfill for missing URL.parse with PDF.js v5 and QtWebEngine < 6.9. Note this is a "best effort" fix and you should be using the "older browsers" ("legacy") build of PDF.js instead.
Removed
- The ua-slack site-specific quirk, as things seem to work better nowadays without a quirk needed.
- The ua-whatsapp site-specific quirk, as it’s unneeded with the default UA change described above.
Fixed
- Crash when trying to use the DocumentPictureInPicture JS API, such as done by the new Google Workspaces Huddle feature. The API is unsupported by QtWebEngine and now correctly disabled on the JS side. (#8449)
- Crash when a buggy notification presenter returns a duplicate ID (now an error is shown instead).
- Crashes when running :tab-move or :yank title at startup, before a tab is available.
- Crash with input.insert_mode.auto_load, when closing a new tab quickly after opening it, but before it was fully loaded. (#3895, #8400)
- Workaround for microphone/camera permissions not being requested with QtWebEngine 6.9.0 on Google Meet, Zoom, or other pages using the new <permission> element. (#8539)
- Resolved issues in userscripts:
- qute-bitwarden will now prompt a re-login if its cached session has been invalidated since last used. (#8456)
- qute-bitwarden, -lastpass and -pass now avoid a DeprecationWarning from the upcoming 6.0 release of tldextract

Removed
- 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)
Changed
- 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).
Fixed
- 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)

Check the changelog for changes in this release.

Check the changelog for changes in this release.