fenced-frame
| first-party-sets | fenced-frame | |
|---|---|---|
| 3 | 3 | |
| 254 | 118 | |
| 4.3% | 3.4% | |
| 5.2 | 8.0 | |
| 12 days ago | 1 day ago | |
| Bikeshed | Bikeshed | |
| - | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
first-party-sets
-
New in Chrome 113
https://github.com/WICG/first-party-sets#non-goals has:
Non-goals: ... Information exchange between unrelated sites for ad targeting or conversion measurement.
To get something onto the list (https://github.com/GoogleChrome/first-party-sets/blob/main/f..., currently empty) you need to make a public PR with rationale (https://github.com/GoogleChrome/first-party-sets/blob/main/F...). It doesn't look to me like DoubleClick would qualify?
- Public Suffix List Problems
-
A new way for Google to kill your SaaS startup
How would you propose handling this with DNS? Here are some things it covers:
* a.example.com and b.example.com are the same site
* a.co.uk and b.co.uk are not the same site
* a.cloudfront.net and b.cloudfront.net are not the same site
* a.higashikawa.hokkaido.jp and b.higashikawa.hokkaido.jp are not the same site
* a.example.higashikawa.hokkaido.jp and b.example.higashikawa.hokkaido.jp are the same site
There is a proposal to do something similar using .well-known urls: https://github.com/privacycg/first-party-sets
fenced-frame
- Fenced Frames Element
-
Public Suffix List Problems
Yes, that's a known problem. The only proposed solution I've seen so far is Fenced Frames (https://github.com/shivanigithub/fenced-frame).
I don't know if that would even work in your use case, as it's still very limited.
-
Google Chrome Privacy / Fenced Iframes / 3rd party verification vendors
The idea of Fenced Frames is that what is inside can't touch the outside and visa versa, think of it like a more severe version of Sandbox that doesn't impact interactivity with the frame. So some of the problems that have to be addressed with the future of privacy proposal def include IVT, viewability and brand safety measurement, which often occurs with scripts crawling out of the frame. The proposal goes into some use cases: https://github.com/shivanigithub/fenced-frame
What are some alternatives?
psl-problems
related-website-sets
chromium - The official GitHub mirror of the Chromium source
issues - WiX Toolset Issues Tracker