summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFlorian Bruhin <me@the-compiler.org>2022-06-22 15:30:45 +0200
committerFlorian Bruhin <me@the-compiler.org>2022-06-22 15:30:45 +0200
commitf0436c0d68604c06b2a2f384653fb10ab0b1ca15 (patch)
tree98874528d081c125d67ff6f3d87f218b569b7675
parent38a26a7ff8d153b6b1b457b9d788e605fe42ce7d (diff)
downloadqutebrowser-f0436c0d68604c06b2a2f384653fb10ab0b1ca15.tar.gz
qutebrowser-f0436c0d68604c06b2a2f384653fb10ab0b1ca15.zip
Update changelog from master
-rw-r--r--doc/changelog.asciidoc30
1 files changed, 30 insertions, 0 deletions
diff --git a/doc/changelog.asciidoc b/doc/changelog.asciidoc
index dae743ad9..bf37a64d2 100644
--- a/doc/changelog.asciidoc
+++ b/doc/changelog.asciidoc
@@ -15,6 +15,36 @@ breaking changes (such as renamed commands) can happen in minor releases.
// `Fixed` for any bug fixes.
// `Security` to invite users to upgrade in case of vulnerabilities.
+[[v2.5.2]]
+v2.5.2 (unreleased)
+-------------------
+
+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.
+
[[v2.5.1]]
v2.5.1 (2022-05-26)
-------------------