3 ms·
There's movement from the Internet Advertising Bureau, they explicitly say that this signal must be adhered to if the header is present, and this signal must be
by secondcoming 2y ago
There's movement from the Internet Advertising Bureau, they explicitly say that this signal must be adhered to if the header is present, and this signal must be forwarded to Demand Side Platforms.
- JimDabell 2y agoI mean is there any movement in getting major browsers to adopt this? Normally when a spec. like this is written that needs adoption from web browsers, an explainer is written and then the major rendering engines are asked for their feedback. For instance, here’s an explainer: https://github.com/krgovind/first-party-sets https://github.com/krgovind/first-party-sets Here’s where WebKit was asked for their position on it: https://github.com/WebKit/standards-positions/issues/93 https://github.com/WebKit/standards-positions/issues/93 Here’s where Mozilla was asked for their position on it: https://github.com/mozilla/standards-positions/issues/350 https://github.com/mozilla/standards-positions/issues/350 Here’s the process Blink goes through to get a new feature like this going: https://www.chromium.org/blink/launching-features/ https://www.chromium.org/blink/launching-features/ I tried to find where this was done for GPC and couldn’t find anything. Did they just write a spec. and not bother doing any of the work involved in getting it adopted? Or is there progress being made that I didn’t see? Hence my question: Is there any movement on this at all? Or is the process of getting it adopted by Blink and WebKit at absolute zero?
- secondcoming 2y agoI have no idea about browser adoption. I’m just aware of adtech’s requirements around it.