krgovind

Results 61 comments of krgovind

That's an excellent question! Unfortunately, the current design doesn't allow for this. We did consider designing FPS so that it is specified as origins, see the [alternative design](https://github.com/privacycg/first-party-sets#origins-instead-of-registrable-domains) section; but...

Hi @LuHuangMSFT - just pinging this discussion to see if you are able to expand upon the motivation/use-case behind your question.

@LuHuangMSFT Could you expand on the warning UI that is displayed? Is it a warning displayed by the browser, or by the destination origin? Or perhaps, were you referring to...

+1 to what @davidben wrote. For the case of PWAs, something explicit like [`scope_extensions`](https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md) would indeed be preferable. We had a similar discussion about how FPS could apply to cache...

@joelodom - FYI, we recently published a proposal for an [opt-in cookie partitioning attribute](https://github.com/DCtheTall/CHIPS). I'd like to welcome your feedback on usefulness and support for incubation in a standards group...

Thanks for the discussion here, everyone! ----- Responding to @martinthomson > First-party sets (FPS) violates some central principles of the modern web. Specifically, the priority of constituencies puts user interests...

> We haven't decided on details but the idea is to consider a bounce/redirect that isn't between two domains in the same first party set as a candidate for being...

Responding to @johnwilander > > Does that mean if I have a First-Party Set with sites {A, B, C}, the "bounce" pattern A->B->C->A would not be classified as tracking; but...

Responding to @johnwilander > Exempting certain scenarios is not the right framing. This is about finding a path to prevent known cross-site tracking while not breaking legitimate use cases. Blocking,...

> I don't think the page has to be blocked, just that embeds have thier cookies partitioned unless the browser has set an internal "consented" flag for an embed's origin....