[qutebrowser] qutebrowser v2.5.2 released: More regression and notification fixes!

[Bob Crochelt]

Florian,
Thanks for this work!
-- 
Regards,

Bob Crochelt
Ukiah, California, USA
406.942.0847


On Wed, Jun 22, 2022 at 03:41:24PM +0200, Florian Bruhin via qutebrowser wrote:
> Hey,
> 
> I'm happy to announce that I just released qutebrowser 2.5.2!
> 
> This is another bugfix release full of... duh bugfixes (and hopefully
> no new bugs this time, like it happened with the notification fixes in
> 2.5.1 which actually made notifications less stable instead of more...).
> 
> Then again, this also squashes a bug which have been around since 2018,
> so, it must be good! Here is the full changelog:
> 
> - 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.
> 
> Enjoy!
> 
> Florian
> 
> -- 
>             me at the-compiler.org | https://www.qutebrowser.org 
>        https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
>        GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
>              I love long mails! | https://email.is-not-s.ms/