From: datenwolf <datenwolf@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Can we please keep firefox-esr-78 available for the forseeable future?
Date: Tue, 30 Nov 2021 23:04:24 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34328@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
New issue by datenwolf on void-packages repository
https://github.com/void-linux/void-packages/issues/34328
Description:
I just noticed that `firefox-esr` got bumped to version 91.3.0 since my last full system upgrade. Now personally my experiences with the 9x versions of Firefox were a bugfest. All of the bugs I did encounter also manifested for other users and are accounted for and confirmed in the Firefox bugzilla bugtracker.
Unfortunately those are not minor things. There are UI bugs like attempting to type in the search bar randomly focusing a different UI element. Tabbar height miscalculated if website titles make use of Unicode codepoints that require to use fonts with a different base height. Typing long text into multiline edits cause segfault tab crashes. WebGL no longer works properly, etc., etc.
After months of enduring those bugs without them being resolved I downgraded back to firefox-esr-78. For the time being I've put that package on hold on my systems. But it'd be nice if we could have this specific version being available until the structural issues of Firefox development have been resolved.
next reply other threads:[~2021-11-30 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 22:04 datenwolf [this message]
2021-12-04 12:52 ` q66
2021-12-04 12:52 ` [ISSUE] [CLOSED] " q66
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34328@inbox.vuxu.org \
--to=datenwolf@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).