Hello, Is there a crbug tracking implementation of this feature?
Thanks Kevin From: Mike Taylor <miketa...@chromium.org> Sent: Thursday, April 3, 2025 5:38 AM To: Ashley Gullen <ash...@scirra.com>; Chromestatus <ad...@cr-status.appspotmail.com> Cc: blink-dev@chromium.org; antoniosart...@google.com; dr...@google.com; mk...@google.com; riz...@google.com; ta...@google.com Subject: [EXTERNAL] Re: [blink-dev] Intent to Prototype: Limiting Access to Local Fonts 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 On 4/3/25 4:32 AM, 'Ashley Gullen' via blink-dev wrote: Presumably this does not affect the Local Font Access API (queryLocalFonts())? Once that method has resolved will the returned fonts then be allowed to be used in font rendering? On Wed, 2 Apr 2025 at 22:36, Chromestatus <ad...@cr-status.appspotmail.com<mailto:ad...@cr-status.appspotmail.com>> wrote: Contact emails ta...@google.com<mailto:ta...@google.com>, riz...@google.com<mailto:riz...@google.com> Explainer https://github.com/explainers-by-googlers/limiting-local-fonts-access?tab=readme-ov-file Specification None Summary 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. Blink component Blink>Fonts<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EFonts%22> Motivation 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. Initial public proposal https://github.com/explainers-by-googlers/limiting-local-fonts-access TAG review None TAG review status Pending Risks Interoperability and Compatibility None Gecko: Shipped/Shipping (https://support.mozilla.org/en-US/kb/firefox-protection-against-fingerprinting#:~:text=Enable%20Fingerprinting%20Protection%3A%20To%20control,Known%20fingerprinters%20and%20Suspected%20fingerprinters) WebKit: Shipped/Shipping (https://webkit.org/tracking-prevention) Web developers: No signals Other signals: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? None Debuggability None Is this feature fully tested by web-platform-tests<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>? No Flag name on about://flags None Finch feature name None Non-finch justification None Requires code in //chrome? False Estimated milestones DevTrial on desktop 138 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5185489285677056?gate=5188393555984384 This intent message was generated by Chrome Platform Status<https://chromestatus.com/>. -- 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+unsubscr...@chromium.org<mailto:blink-dev+unsubscr...@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<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67edade5.170a0220.2d63e1.0a6e.GAE%40google.com?utm_medium=email&utm_source=footer>. -- 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+unsubscr...@chromium.org<mailto:blink-dev+unsubscr...@chromium.org>. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAABs73hDOiXbEBdE%3DBj%2Bh_4AZjOCaszW_u2xKKehfsRQE%3DScyA%40mail.gmail.com<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAABs73hDOiXbEBdE%3DBj%2Bh_4AZjOCaszW_u2xKKehfsRQE%3DScyA%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- 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+unsubscr...@chromium.org<mailto:blink-dev+unsubscr...@chromium.org>. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/09f7c28a-9062-4d88-919b-ebbdd0dfc466%40chromium.org<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/09f7c28a-9062-4d88-919b-ebbdd0dfc466%40chromium.org?utm_medium=email&utm_source=footer>. -- 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+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CH4PR00MB2496F483ECA2105858F117A0C0B32%40CH4PR00MB2496.namprd00.prod.outlook.com.
