stoically

This should usually work as it should be covered by the "persistent events on startup" provided by the Firefox API. To debug this further a {debug log](https://github.com/stoically/temporary-containers/wiki/Debug-Log) would help.

> Basically, when Paypal is done and I get sent back to example.org, TC determines that there's already an existing container spawned for example.org, and so it reuses that, which...

Interesting use case. This would require some sort of queuing mechanism as currently it's really just a random asynchronous race if multiple requests come in, so expected behavior.

Domain grouping sounds like a good approach. Some prior discussions on the topic: https://github.com/stoically/temporary-containers/issues/407, https://github.com/stoically/temporary-containers/issues/432#issuecomment-665087742 Would probably make sense to implement that with #397

Yeah, it's weird that containers don't cover that, must be a bug. I guess I could add the ETag Stoppa functionality as advanced preference into TC as well :thinking:

[ClearURLs](https://addons.mozilla.org/firefox/addon/clearurls/) filters ETag headers by default as well.

Should be fixed by Firefox 85+

Hm, true. So they missed Etag in their attempt to fix the supercookie problem (https://blog.mozilla.org/security/2021/01/26/supercookie-protections/)? oof

Seems like you misconfigured something, maybe provide your exact configuration. If I open `example.org` in a new container tab and have `www.iana.org` globally excluded, it stays in the same container...

Ah, so you're actually looking for a way to force pages to open in no container. Yeah, that's not supported by TC currently and is different from excluding things from...