From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Firefox 112 invisible text
Date: Thu, 13 Apr 2023 14:05:17 +0200 [thread overview]
Message-ID: <20230413120517.xJVQyL0yI2J1r6R3gSajwNxhIYnwDcUBtY6PJLWG-3s@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: 679 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/43416#issuecomment-1506850290
Comment:
> 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.
There have been other reports for different debian https://www.reddit.com/r/firefox/comments/12jm9ju/on_firefox_112_font_goes_white_on_some_sites_linux/
The steps to reproduce and the overall information in this is simply not enough to debug this any further as this is not affecting everyone.
Would be ineresting to find out which fonts are used on the broken sites and if they are system fonts etc.
next prev parent reply other threads:[~2023-04-13 12:05 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 [this message]
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 ` [ISSUE] [CLOSED] " Duncaen
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=20230413120517.xJVQyL0yI2J1r6R3gSajwNxhIYnwDcUBtY6PJLWG-3s@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).