ممتاز هام جدا لمنع موقع تويتر من التجسس على المواقع التى تفتحها

When you have Twitter Container and Amazon Container both installed, Firefox will open X/Twitter in the Amazon container, despite instructing it specifically to open it in the Twitter container.

I don't know exactly which container to blame but I'm mentioning it here.
For that functionality to work, I now have to remove this addon.

When I had this installed, it caused problems with tabs. If I logged into Twitter, logged out and then went to Facebook, 2 Facebook tabs would pop up. Same thing going the other way. Uninstalling the extension fixed things.

please fix each time i close firefox, the tab that was pined then it goed unpined , it cant stay pined. Please fix it.

The containerised tab will not stay pinned. At every restart the tab opens unpinned. After re-pinning the same thing happens again on next restart.

Aight

When I want to log into another account I open a container tab for that account, then go to twitter.com. However, I think that this extension is changing the container of the tab to the Twitter container. So what I want to suggest is that you don't change the container if the tab is already running in a container. I am disabling the extension.

Serious bugs in the Facebook-container extension code involving triggering actions on URL change / container change.

- Clicking links / changing URLs in omni-box from container site to container site will close the current tab (history lost) and opens two tabs to new container site
- Clicking links container site to non- container site working okay (one new tab opened, history container maintained)
- For Google container add-on sometimes when clicking on link in search results, it will not open a new tab but opens a new site in the current container (login session lost). This means Google is not separated from other sites. Also occurs when typing in the omni-box
- Changing URLs in omni-box from container site to non- container (and visa versa) will close current tab (it should open a new tab instead of closing the container tab although arguable)
- No problems while staying in same container

*** TESTED ***

All container add-ons are conflicting as a result (you can only use one). Mozilla needs to change the code that triggers actions (triggered twice going from container to container site using multiple add-ons).
Conclusion: You cannot fork the Facebook container add-on without rewriting the code.

This container appears to containerize Twitter, but it does not appear to containerize all Twitter tracking.

The Facebook Container (which Twitter Container claims to based on) disables the Facebook button on pages so that Facebook cannot receive a link indicating you had visited that page. The Twitter container does NOT disable those buttons, and clicking on them will allow Twitter to track how you arrived at Twitter. THIS IS BAD!!!

Also, the Twitter Container does not add an icon to the menu bar like other add-ons.

A start, but not a lot of added capability over Multi-Account Containers, and definitely not as containerized as it should be.

very bad, it log out

kinldy add mobile.twitter.com as well to the list of urls
Thanks for the addon

Works great. My browser logs out of Twitter every day or two when I use it. That doesn't happen with Facebook Container or Google Container.