summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFlorian Bruhin <me@the-compiler.org>2022-06-22 15:30:14 +0200
committerFlorian Bruhin <me@the-compiler.org>2022-06-22 15:30:14 +0200
commit5d75fcf1db444c388e23625e2375ed72ea132c0a (patch)
treefa07248c5b6cd5ca0d4322c653f8f923e4a4b679
parent47ef35fb311cdf2023cc450d0b6ef6e986b27474 (diff)
downloadqutebrowser-5d75fcf1db444c388e23625e2375ed72ea132c0a.tar.gz
qutebrowser-5d75fcf1db444c388e23625e2375ed72ea132c0a.zip
Update changelog
-rw-r--r--doc/changelog.asciidoc22
1 files changed, 12 insertions, 10 deletions
diff --git a/doc/changelog.asciidoc b/doc/changelog.asciidoc
index 9e682398e..3fb438552 100644
--- a/doc/changelog.asciidoc
+++ b/doc/changelog.asciidoc
@@ -105,13 +105,18 @@ v2.5.2 (unreleased)
Fixed
~~~~~
-- 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.
+- 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
@@ -119,9 +124,6 @@ Fixed
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.
-- 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.
- 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.