You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to me that the "leaking" issue may be largely solved by clearing all cookies, localstorage etc before moving tabs between containers? (which forces fresh login in the new container - password manager ffunctions in all containers)
Would be great if the tabs could be moved in their unloaded state, with tab name and history - if current page fails to load, at least you can know what it is, hit back button and re-click the link to it...
(I use tab ReTitle as well, titles are preserved between FF sessions so hopefully can be kept when moving between containers... )
hey: sorry for the very late reply: I was kind of off the grid for a while :/
nope: cookies, localstorage, etc. are not the problem here as they get all discarded.
The problem occurs, if the website encodes identifiers within the urls ... an overly obvious example would be something like:
http://example.com?mysession=0123456789
now: if you open this url in another container, the web page could re-identify you with via the mysession parameter.
Hi, I see you closed this, does that mean that conex DOES move tabs unloaded? Or are you looking at achieving this through the issue at drag/drop support in conex popup #84?
It seems to me that the "leaking" issue may be largely solved by clearing all cookies, localstorage etc before moving tabs between containers? (which forces fresh login in the new container - password manager ffunctions in all containers)
Would be great if the tabs could be moved in their unloaded state, with tab name and history - if current page fails to load, at least you can know what it is, hit back button and re-click the link to it...
(I use tab ReTitle as well, titles are preserved between FF sessions so hopefully can be kept when moving between containers... )
(Related to #225)
The text was updated successfully, but these errors were encountered: