The goal of the project is to create a very customizable experience while including a few suggested uses for users who may not want as much control. They can choose to send the state from their personal context or work context, and they can choose to create a new, short-lived state to browse in a certain context for a few days until a task is completed. The containers project inserts a user-controlled key into storage via OriginAttributes, which allows users to decide which state to use when interacting with a site. Cookies can be managed with the Cookie manager, but all other state has no graphical interface for management (see Bug 1147820). The current level of control is very coarse, essentially providing an "all or nothing" solution users can clear everything or accept everything. This includes both the default container and in any of the predefined containers.Īt an abstract level, the feature seeks to give users more control over the data websites can access (ex: cookies, localStorage, indexedDB, etc). The new tab will open within the same container as the previous tab. Holding the "Control" key on Windows or Linux (or the "Command" key on Mac) while clicking a link will open it in a new tab. Right click on any link, select "Open link in New Container Tab", and then select the desired container tab. It's possible to open links in a new and/or different container. After choosing one of these, you will see a new tab from that container appear in the tab strip. From here you can choose from one of the four pre-defined containers (Home, Work, Banking, and Shopping). In the OS menu bar, click "File" -> "New Container Tab". There are several ways to open new containers: Likewise, any browsing you do within the new container will not affect the preferences, logged in sessions, or tracking data of your other containers. This means your site preferences, logged in sessions, and advertising tracking data won't carry over to the new container. Your normal tabs, which we consider to exist in the default container, will still look and act as you'd expect them to before enabling containers.Ĭontainer tabs operate just as you would expect a normal tab to, except for the fact that the sites you visit will have access to a separate slice of the browser's storage. You will have the option to open entirely new browsing contexts, which will have their browser storage (such as cookies or localStorage) separated from other containers. When enabled, containers will integrate seamlessly into your current browsing experience. The containers feature is enabled in Firefox Nightly 50 by default with the about:config pref `` set to true. Each context will have its own local state which is separated from the state of other contexts. The goal of this project is to allow users to separate these different contexts while browsing the web on Firefox. They may not want to mix their social network context with their work context. Similarly, users have different contexts when they browse the web. The way they act at work may differ from how they act with their family. Individuals behave differently in the world when they are in different contexts. 5.1 What is (and isn't) separated between Containers.2.2 Open links in new tabs and containers.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |