Closed Bug 1355979 Opened 8 years ago Closed 8 years ago

Containers: new tabs should be created in the container of origin

Categories

(Firefox :: General, enhancement)

52 Branch
enhancement
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: grgwmsm, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce: Installed Containers (https://testpilot.firefox.com/experiments/containers). Created a WORK container and opened site-1. While viewing site-1 in the WORK container-tab, I tapped Ctrl+N. Actual results: A new tab was created, but the new tab was not in the WORK container (even though I was in a WORK container-tab when I tapped Ctrl+N). The new tab was created in NO container (ie, just a regular tab). Expected results: The idea of containers is to confine/demarcate your work, but this isn't usable if new tabs are not created in the container I'm working in. If I'm in a WORK container when I tap Ctrl+N, the new tab should be created in the WORK container. When I tap Ctrl+N, the new tab should take on whatever container I was in when I created it.
Severity: normal → enhancement
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Component: Untriaged → General
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.