From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Firefox 112 invisible text
Date: Wed, 26 Apr 2023 00:54:02 +0200 [thread overview]
Message-ID: <20230425225402.uRxoXOD3Q5bnyKl_2RJVZmCe3CJW-4JsFJb_5lO8HV8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43416@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
Closed issue by someone13574 on void-packages repository
https://github.com/void-linux/void-packages/issues/43416
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.21_1 x86_64 AuthenticAMD uptodate rrrrmmdnFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Void 6.1.21_1 x86_64-musl GenuineIntel uptodate rrnFFFFF
### Package(s) Affected
firefox-112.0_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Text rendering would work as in previous versions.
### Actual behaviour
A number of sites have text which isn't rendering. Some sites I've found which demonstrate this are [Github (as the largest site I've found)](https://github.com/void-linux/void-packages), [common crawl](https://commoncrawl.org/), and a few confirmation emails where the confirmation code is there (I can copy it) but invisible.
I am not sure if this is a Void specific problem but I've not seen any other reports of it so I am leaning in that direction.
### Steps to reproduce
1. Update Firefox to version 112.0
2. Go to [https://github.com/void-linux/void-packages](https://github.com/void-linux/void-packages)
3. Observe invisible text
prev parent reply other threads:[~2023-04-25 22:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 1:00 [ISSUE] " someone13574
2023-04-13 9:43 ` devlocalhost
2023-04-13 9:43 ` devlocalhost
2023-04-13 12:05 ` Nidrop
2023-04-13 12:05 ` Duncaen
2023-04-13 14:04 ` ircurry
2023-04-13 15:55 ` Adailoe
2023-04-13 16:00 ` Duncaen
2023-04-13 16:10 ` Adailoe
2023-04-13 19:17 ` Nidrop
2023-04-13 21:18 ` Nidrop
2023-04-13 23:14 ` SavageMessiah
2023-04-14 1:28 ` ircurry
2023-04-14 7:03 ` Anachron
2023-04-14 7:05 ` Anachron
2023-04-14 8:17 ` Nidrop
2023-04-14 9:40 ` Nidrop
2023-04-14 11:35 ` Adailoe
2023-04-15 6:33 ` PurpleVsGreen
2023-04-15 11:52 ` Anachron
2023-04-18 3:24 ` rickalex21
2023-04-18 11:18 ` Anachron
2023-04-19 12:28 ` fosslinux
2023-04-19 14:54 ` Anachron
2023-04-19 14:54 ` Anachron
2023-04-19 16:36 ` Nidrop
2023-04-22 14:37 ` Nidrop
2023-04-25 19:47 ` Nidrop
2023-04-25 22:54 ` Duncaen [this message]
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=20230425225402.uRxoXOD3Q5bnyKl_2RJVZmCe3CJW-4JsFJb_5lO8HV8@z \
--to=duncaen@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).