-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Closed
brave/brave-core
#8468Labels
OS/AndroidFixes related to Android browser functionalityFixes related to Android browser functionalityOS/DesktopQA Pass - Android ARMQA Pass - Android TabQA Pass-LinuxQA Pass-Win64QA Pass-macOSQA/Test-All-PlatformsQA/Yespriority/P2A bad problem. We might uplift this to the next planned release.A bad problem. We might uplift this to the next planned release.privacyprivacy/chromium-redqueenWork to remove or improve privacy-harming "features" added in Chromium.Work to remove or improve privacy-harming "features" added in Chromium.release-notes/include
Milestone
Description
Currently Brave disables the FLoC component. However there is other FLoC functionality shipped in Chromium (behind origin trials). We should disable FLoC completely in Brave, including:
- FLoC client-side determinations of cohorts
- Any reporting of FLoC cohort determinations to Google (or otherwise) servers (i.e., the reporting used for k-anonymity cohort protections)
- FLoC JS methods (i.e.
document.interestCohort
) - Any UI related to the FloC permission (i.e.,
interest-cohort
)
dabat, SiliconAvatar, dentistformyeye, Furax-31, mikhoul and 24 moremikhoul, vsvito420, danisztls and sudoAlphaXkron4eg, mikhoul, awave1, dtsudo, Julian and 9 morevsvito420 and danisztlsdashed, intrnl, GGAlanSmithee and danisztls
Metadata
Metadata
Assignees
Labels
OS/AndroidFixes related to Android browser functionalityFixes related to Android browser functionalityOS/DesktopQA Pass - Android ARMQA Pass - Android TabQA Pass-LinuxQA Pass-Win64QA Pass-macOSQA/Test-All-PlatformsQA/Yespriority/P2A bad problem. We might uplift this to the next planned release.A bad problem. We might uplift this to the next planned release.privacyprivacy/chromium-redqueenWork to remove or improve privacy-harming "features" added in Chromium.Work to remove or improve privacy-harming "features" added in Chromium.release-notes/include