From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qutebrowser: update to 3.0.0, use Qt6 by default
Date: Tue, 22 Aug 2023 08:41:08 +0200 [thread overview]
Message-ID: <20230822064108.YBbgjbvDR-qEwhm9aAoQD7zbGw5m3bN1teI1f9kgXTk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45665@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/45665#issuecomment-1687557689
Comment:
I imagine the font rendering issue can be worked around by disabling bitmap fonts as was the case with recent Firefox updates. This with a compelling need for bitmap fonts (I'm curious to know what such a need might be) can either build the browser with the `qt6` option disabled, or just manually install the Qt5 dependencies and pick that version with a command-line flag.
The fact that `qt5-webengine` is stuck at Chromium 8x and increasingly triggers warnings from websites looking to drop support (or functionality altogether) strongly motivates the move to Qt6 by default wherever possible.
next prev parent reply other threads:[~2023-08-22 6:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 20:33 [PR PATCH] " ahesford
2023-08-21 22:33 ` loosefish-scapegrace
2023-08-22 6:41 ` ahesford [this message]
2023-08-22 6:41 ` ahesford
2023-08-22 6:42 ` ahesford
2023-08-22 7:18 ` [PR PATCH] [Updated] " ahesford
2023-08-24 21:55 ` [PR PATCH] [Merged]: " ahesford
2023-09-07 21:58 ` vlur
2023-09-08 0:21 ` loosefish-scapegrace
2023-09-08 0:37 ` vlur
2023-09-08 1:43 ` ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230822064108.YBbgjbvDR-qEwhm9aAoQD7zbGw5m3bN1teI1f9kgXTk@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).