Limits the fonts websites can use to only the default system fonts installed by the operating system. The unique set of locally installed fonts can be used for cross-site user tracking by measuring the side-effects of font rendering. By restricting user-installed font access, we aim to improve user privacy.
Users have unique font collections on their devices, and this uniqueness can be exploited to track them across the web by analyzing font rendering. This undermines user privacy by allowing websites to re-identify individuals. To mitigate this privacy risk, a solution is needed to limit websites' access to a user's set of locally installed fonts. Recent CSS working group discussions have also brought up the idea of prescribing user agents to not expose user-installed fonts on the web as a privacy protecting measure. These measures mirror Safari’s approach of limiting local font availability by restricting to fonts that are bundled with the operating system by default.
None
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
DevTrial on desktop | 138 |
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67edade5.170a0220.2d63e1.0a6e.GAE%40google.com.
That seems to be covered in a few places in the explainer, but
most clearly at
https://github.com/explainers-by-googlers/limiting-local-fonts-access?tab=readme-ov-file#limiting-to-local-fonts-will-break-my-application-what-should-i-do
--
Hello,
Is there a crbug tracking implementation of this feature?
Thanks
Kevin
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/09f7c28a-9062-4d88-919b-ebbdd0dfc466%40chromium.org.