Bug 1852176 Comment 7 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Masatoshi Kimura [:emk] from comment #2)
> This is intentional change by bug 1826408. You can set the `layout.css.font-visibility.private` pref value to `3` to restore the old behavior.

Correction: I think this preference (`layout.css.font-visibility.private`) was removed in bug 1847599, specifically here:
  https://hg.mozilla.org/mozilla-central/rev/eb06ef97c8af#l2.28

So I suspect the most-direct way to get back the old behavior here is to change `privacy.fingerprintingProtection.pbmode` to `false` (which is the preference that bug 1849903 enabled beyond Nightly in version 118).
(In reply to Masatoshi Kimura [:emk] from comment #2)
> This is intentional change by bug 1826408. You can set the `layout.css.font-visibility.private` pref value to `3` to restore the old behavior.

Correction: I think this preference (`layout.css.font-visibility.private`) was removed in bug 1847599, specifically here:
  https://hg.mozilla.org/mozilla-central/rev/eb06ef97c8af#l2.28

~So I suspect the most-direct way to get back the old behavior here is to change `privacy.fingerprintingProtection.pbmode` to `false` (which is the preference that bug 1849903 enabled beyond Nightly in version 118).~ [EDIT: see  bug 1852239 comment 3 for the recommended pref/value to use to restore the old behavior.]
(In reply to Masatoshi Kimura [:emk] from comment #2)
> This is intentional change by bug 1826408. You can set the `layout.css.font-visibility.private` pref value to `3` to restore the old behavior.

Correction: I think this preference (`layout.css.font-visibility.private`) was removed in bug 1847599, specifically here:
  https://hg.mozilla.org/mozilla-central/rev/eb06ef97c8af#l2.28

~So I suspect the most-direct way to get back the old behavior here is to change `privacy.fingerprintingProtection.pbmode` to `false` (which is the preference that bug 1849903 enabled beyond Nightly in version 118).~ [EDIT: see the end of bug 1852239 comment 3 for the recommended pref/value to use to restore the old behavior.]

Back to Bug 1852176 Comment 7