Error with Permissions-Policy header: Unrecognized feature: 'interest-cohort'.

[frederikhors]

Describe the bug
Warning in console:

Error with Permissions-Policy header: Unrecognized feature: 'interest-cohort'.

To Reproduce
svelte-kit init

Information about your SvelteKit Installation:

Diagnostics

• The output of npx envinfo --system --npmPackages svelte,@sveltejs/kit,vite --binaries --browsers:

  System:
  OS: Windows 10 10.0.19042
  Binaries:
  Node: 14.17.0 - C:\Program Files\nodejs\node.EXE
  npm: 7.13.0 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
  @sveltejs/kit: 1.0.0-next.108 => 1.0.0-next.108
  svelte: 3.38.2 => 3.38.2
  vite: 2.3.3 => 2.3.3

• Your browser: Chrome 90

• Your adapter (e.g. Node, static, Vercel, Begin, etc...): static

[dummdidumm]

This is a result of #1263 . You either can opt in to floc if you want to, or just ignore this.

[frederikhors]

I am always of the opinion that a default browser warning is wrong.

[bugs181]

I am always of the opinion that a default browser warning is wrong.

Then you may wan't to complain to Google for introducing this "feature" to begin with. ;)
Google is an analytics company and not all of it's users deserve to have their privacy invaded with an "opt-out" feature. The browser is complaining because it's not letting the browser fingerprint you.

You can read more about it here and here

I'm actually of the mindset that I LOVE that the Svelte team made it an "opt-in" feature, instead of the other way around.

[jonathanstanley]

One way to address this is to edit your svelte.config.js to allow FLoC during development-only.

const config = {
  // etc...
  kit: {
    // etc...
    floc: process.env.NODE_ENV === "development",
  },
};

IMO, I would only do that if developing using Brave browser. Brave has entirely disabled FLoC at the browser level 🤩. Otherwise development is essentially the same as Google Chrome.

See also: brave/brave-browser#14942 (comment)