Open
      
        Bug 1283495
      
      
        Opened 9 years ago
          Updated 3 years ago
      
        
    
  
Add the ability to assign a window to a container
Categories
(Core :: DOM: Security, defect, P3)
        Core
          
        
        
      
        
    
        DOM: Security
          
        
        
      
        
    Tracking
()
        NEW
        
        
    
  
| Tracking | Status | |
|---|---|---|
| firefox50 | --- | affected | 
| firefox57 | --- | fix-optional | 
People
(Reporter: jimm, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [userContextId][domsecurity-backlog])
Add the ability to open a new window where every tab is associated with a particular container. Brownie points for the ability to assign a container to an existing window which would trigger a reload of all tabs using the new identity.
| Comment 1•9 years ago
           | ||
Thanks for the suggestions Jim!
Priority: -- → P3
Whiteboard: [userContextId][domsecurity-backlog]
| Comment 2•9 years ago
           | ||
Bram, can you add something to the about:containers UI that would let a user specify they want a) either all containers in a new window, or b) specific containers in a new window.  Not sure if it should be global or container specific.
Flags: needinfo?(bram)
Priority: P3 → P2
|   | ||
| Comment 3•9 years ago
           | ||
I would suggest having Container Tabs (which can exist in any window) and Container Windows (which can only spawn container tabs of the same type) as modes that you can switch back and forth, instead of ones that can coexist (which would be confusing).
I’m still torn on whether to have this setting be located on about:preferences or about:containers. My gut says the former, but I struggle to explain it in a short, understandable way.
Here’s my take:
Containers        Learn more
[x] Enable
(If enabled, the section below will show up)
Containers will:
(o) Open in a new window
( ) Open in a new tab
What’s a good way to describe these settings?
Flags: needinfo?(bram)
| Updated•9 years ago
           | 
Priority: P2 → P3
Whiteboard: [userContextId][domsecurity-backlog] → [userContextId][domsecurity-backlog2]
| Updated•9 years ago
           | 
Priority: P3 → P2
Whiteboard: [userContextId][domsecurity-backlog2] → [userContextId][domsecurity-*]
| Updated•9 years ago
           | 
Whiteboard: [userContextId][domsecurity-*] → [userContextId][domsecurity-backlog]
| Updated•8 years ago
           | 
Priority: P2 → P3
| Comment 4•8 years ago
           | ||
Bulk change per https://bugzilla.mozilla.org/show_bug.cgi?id=1401020
          status-firefox57:
          --- → fix-optional
Or, another possible solution is, each window just has "default container" for new tabs. I.e., even such window can have no container tabs and other container tabs.
| Updated•3 years ago
           | 
Severity: normal → S3
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•