1829160 - font-visibility pref also affects the browser chrome

Status: VERIFIED FIXED

(Core :: Privacy: Anti-Tracking, defect)

Description

[Martin Balfanz [:mbalfanz]]

Attachment: font-visibility-3.png

When setting font-visibility to 1 or 2, it appears like font access is limited for the entire browser, including the browser chrome.

STR

• open a private window and navigate to https://nqo.wikipedia.org/wiki/
• with font-visibility set to 3, observe the address bar/tab bar
• change font-visibility to 1 or 2 in about:config
• observe the address bar/tab bar again on the page mentioned above

AR

• address bar and tab bar show tofu boxes, similar to the web page content

ER

• address bar and tab bar should show the text in the correct font

Attached are two screenshots, taken on MacOS 13

Comment 1

[Martin Balfanz [:mbalfanz]]

Attachment: font-visibility-2.png

Comment 2

[Tom Ritter [:tjr]]

I'm not sure if this is intended to behave this way, or if this is unintentional...

Comment 3

[Jonathan Kew [:jfkthame]]

I'm inclined to think we should not apply the font visibility restriction to the browser chrome; it's aimed at web content.

Comment 4

[Jonathan Kew [:jfkthame]]

Attachment: Bug 1829160 - Don't apply font-visibility restrictions to chrome contexts. r=#layout-reviewers

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/bea282821e77
Don't apply font-visibility restrictions to chrome contexts. r=dholbert

Comment 6

[Norisz Fay [:noriszfay]]

https://hg.mozilla.org/mozilla-central/rev/bea282821e77

Comment 8

[Ardelean Oana, Desktop Test Engineering [:oardelean]]

Reproducible on a 2023-05-07 Nightly build on macOS 12.
Verified as fixed on Firefox 115.0b9(build ID: 20230622161221) and Nightly 116.0a1(build ID: 20230623092529) on macOS 12, Windows 10, Ubuntu 22.