4 ms·
"Users of browsers that support FLoC can either send real FLoC or random FLoC, but they cannot send no FLoC." Why? I would expect a browser extension to be abl
by jefftk 6y ago
"Users of browsers that support FLoC can either send real FLoC or random FLoC, but they cannot send no FLoC."
Why? I would expect a browser extension to be able to override document.interestCohort to throw an exception?
(Disclosure: I work at Google, speaking only for myself)
- 1vuio0pswjnm7 6y agoMost users never even change defaults let alone install extensions. There is no described option to disable FLoc in the browser. Why not. Surely the design decision not to include an option to disable FLoC was intentional. That's the point I was making.
- Izkata 6y ago> document.interestCohort If that's an actual way to access it, "undefined" will have to be acceptable due to browsers that don't support it.
- jefftk 6y agoYup! Or a Promise that never resolves (since it's async)
- Izkata 6y agoWait, what? Async? Isn't your cohort supposed to be precomputed? And undefined would still have to be handled anyway, as browsers without support wouldn't have the attribute at all (at least for several years after it was accepted, for everything to get the new feature).
- jefftk 6y ago> Async? Isn't your cohort supposed to be precomputed? The explainer indicates it's a Promise: "cohort = await document.interestCohort()" -- https://github.com/WICG/floc https://github.com/WICG/floc One reason to make it async could be to give browsers the option to gate access behind a permissions prompt in some circumstances. > And undefined would still have to be handled anyway, as browsers without support wouldn't have the attribute at all Definitely. There are also browsers that are unlikely to add support (ex: Brave, as we're discussing)