Qutebrowser

Check the [changelog](https://github.com/qutebrowser/qutebrowser/blob/main/doc/changelog.asciidoc) for changes in this release.

Check the [changelog](https://github.com/qutebrowser/qutebrowser/blob/master/doc/changelog.asciidoc) for changes in this release.

**NOTE:** This release is a source-only release, to fix a recent issue with changed sqlite options on FreeBSD. For Windows/macOS binary releases (and any environment where sqlite accepts [double-quoted string literals](https://www.sqlite.org/quirks.html#double_quoted_string_literals_are_accepted)), this release is equivalent to [v2.5.3](https://github.com/qutebrowser/qutebrowser/releases/tag/v2.5.3), thus no new binaries were uploaded here.

Fixed

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

Added

- New `array_at` quirk, polyfilling the [`Array.at` method](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/at), which is needed by various websites, but only natively available with Qt 6.2.

Fixed

- 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

Fixed

- Packaging-related fixes:
* The `install` and `stacktrace` help pages are now included in the docs
shipped with qutebrowser when using the recommended packaging workflow.
* The Windows installer now more consistently uses the configured Windows
colors.
* The Windows installer now bases the desktop/start menu icon choices on
the existing install, if upgrading.
* The macOS release hopefully doesn't cause macOS to (falsely) claim that it
"is damaged and can't be opened" anymore.
- 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.

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:
* With the `tiramisu` notification server (due to invalid behavior of the server, now a non-fatal error)
* With the `budgie` notification server when closing a notification (due to invalid behavior of the server, now worked around)
* When a server exits with an unsuccessful exit status (now a non-fatal error)
* When a server couldn't be started successfully (now a non-fatal error)
* With the `herbe` notification presenter, when the website tries to close
the notification after the user accepting (right-clicking) it.
- Fixes in userscripts:
* The `qute-bitwarden` userscript now correctly searches for entries for
sites on a subdomain of an unrecognized TLD. subdomain names. Previously
`my.site.local` would have searched in bitwarden for `my.sitelocal`,
losing the rightmost dot.