In regards to #1 - we have a feature (WIP right now) that adds the ability to delete data (cache, cookies and local storage) per container. Look for that in a future release.
Hey there! I'm one of the devs on this project. We made some progress last year on per-container proxy support. Follow this issue for (hopefully soon) progress here:
Facebook Container dev here. It breaks those sites because the extension blocks all Facebook resources (and tracking) from loading on non-Facebook sites.
To use Facebook login on a site, you'll need to add the website to the Facebook Container. Follow the directions from the docs[1]. This will stop you from having to turn the extension on and off entirely.
MAC Containers developer here. This treatment is done by default in the Facebook Container add-on. It's more of a question of how to handle the setting on a per domain/Container in the UI.
Sorry to bomb you like this, but I don't have the time/energy to find where to file a ff container bug: twitter.com never opens in it's designated container for me. That is the only site I always have to "Reopen in container".
Same here: that's the only site that doesn't work. I wonder if it has something to do with the post-login redirects: it's impossible to say "always open this site in this container", because you've already been redirected to a different url.
