Add telemetry to determine potential impact of anti-font-fingerprinting measures
Categories
(Core :: Layout: Text and Fonts, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox76 | --- | fixed |
People
(Reporter: jfkthame, Assigned: jfkthame)
References
Details
(Whiteboard: [layout:backlog:76])
Attachments
(3 files)
We are considering measures to limit font-based fingerprinting by restricting the set of fonts that are exposed via CSS font-family
etc.
To better understand the potential impact of such changes, we should add telemetry to find out how frequently users may see rendering differences or breakage.
I propose that as an initial step, we should report:
- How often does a page fail to find any font, and resort to hexbox rendering?
- If the frequency of this rises noticeably when we make changes, that would suggest users are getting a bad experience
- How often does a page use a locally-installed font that was not part of the default (OS-provided) font collection?
- These are fonts that we are considering blocking, which means the rendering of the page would change
- How often does font fallback end up using a non-OS-provided font?
We already have some webfont telemetry in place; this is probably a reasonable place to add installed-font telemetry as well.
Updated•6 years ago
|
Assignee | ||
Comment 1•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 2•6 years ago
|
||
Depends on D66125
Updated•6 years ago
|
Assignee | ||
Comment 3•6 years ago
|
||
Depends on D67787
Comment 4•6 years ago
|
||
Updated•6 years ago
|
Comment 6•6 years ago
|
||
Backed out 4 changesets (bug 1619349, bug 1619350) for causing test_font_whitelist.html to fail
https://hg.mozilla.org/integration/autoland/rev/6f834ef903846d598280d3d1274d626a92bfe863
Comment 8•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/62f8ce89dce8
https://hg.mozilla.org/mozilla-central/rev/1a8269aa3f6e
Assignee | ||
Updated•6 years ago
|
Updated•5 years ago
|
Description
•