Re: [csswg-drafts] [css-fonts] Exploring better ways to balance privacy, i18n, design tradeoffs for local fonts (#11571)

re-sharing an idea from email with @astearns (w/ minor clarity and concision edits)

> Heres an idea: allow the browser to access an unlimited number local fonts *until a look up failed*, after which all subsequent look ups would fail. You’d need to tie that “just one fail” check to the current storage area’s lifetime (otherwise you’d be able to check another font on each page load / session / whatever) and that’d reintroduce the problem over time (since previous checks could be stored in storage).
>
> I wonder what you all think of this idea. I’ve just thought about it now, so im not confident on it. But it has the appealing property of allowing sites to access fonts that are truely necessary to access the page, while preventing fishing for other fonts. I wonder what you think of this idea?


-- 
GitHub Notification of comment by pes10k
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11571#issuecomment-2679700271 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 24 February 2025 21:33:33 UTC