State of dynamic storage epochs?

I was recently reminded of the piece of
https://lists.w3.org/Archives/Public/public-privacy/2019JulSep/0067.html
that says some browsers were moving to «dynamic policies for handling JS
set storage (e.g. there is no single global “storage clear” event to decide
when to reset device Ids against, but lots of small micro, per value
decisions)».

How is that change going? My impression from
https://webkit.org/blog/10218/full-third-party-cookie-blocking-and-more/ is
that Safari never proceeded to having different lifetimes for different
pieces of non-cookie storage? Did Brave? If so, did you notice any
web-compat problems?

Thanks, Jeffrey

Received on Monday, 12 December 2022 18:55:21 UTC