zlacker

[parent] [thread] 5 comments
1. adastr+(OP)[view] [source] 2023-05-26 05:45:01
How is that different from private browsing?
replies(1): >>lolind+11
2. lolind+11[view] [source] 2023-05-26 05:53:51
>>adastr+(OP)
I can have 3+ different temporary containers open at once, each with a distinct set of cookies, whereas private browsing gives me only one extra cookie jar.

It's massively helpful for testing interactions between users.

replies(2): >>adastr+N2 >>skykoo+Oa7
◧◩
3. adastr+N2[view] [source] [discussion] 2023-05-26 06:10:18
>>lolind+11
At least on my chromium variant each private window (not tab: window) gets its own isolated environment.

I frequently use this to log into websites with different user accounts for testing purposes.

replies(1): >>lolind+p5
◧◩◪
4. lolind+p5[view] [source] [discussion] 2023-05-26 06:37:34
>>adastr+N2
Good to know, I'll take a look!
replies(1): >>adastr+321
◧◩◪◨
5. adastr+321[view] [source] [discussion] 2023-05-26 14:12:01
>>lolind+p5
To be a little more explicit, I think you need to spawn a private window from a non-private window to get a new environment. If you do it from another private window it uses the same sandbox.
◧◩
6. skykoo+Oa7[view] [source] [discussion] 2023-05-28 21:36:55
>>lolind+11
And unlike private browsing windows, they persist across browser restarts until all their tabs are closed.
[go to top]