Open
Bug 1272043
Opened 9 years ago
Updated 1 year ago
adding the ability to open containers via the taskbar jump list/dock
Categories
(Core :: DOM: Security, defect, P3)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox49 | --- | affected |
| firefox57 | --- | fix-optional |
People
(Reporter: kjozwiak, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-backlog3][usercontextId])
Attachments
(3 files, 1 obsolete file)
I think it would be a good idea if we added a "Open New Container" or "New Container" context menu under the dock (OSX/Ubuntu) and taskbar (Win). Users can already create private browsing sessions using this method so it only makes sense to also add the ability to open containers.
I've added three screenshots to illustrate each OS and it's current state when right clicking on the shortcut.
| Reporter | ||
Comment 1•9 years ago
|
||
| Reporter | ||
Comment 2•9 years ago
|
||
Updated•9 years ago
|
Whiteboard: [domsecurity-backlog]
Comment 3•9 years ago
|
||
Many questions: Which container/containers do we want to show there? I don't think we want to make the whole list of containers there.
About linux, this seems quite impossible. That menu comes from the firefox.desktop file. On my computer it is in /usr/share/applications/firefox.desktop
Now, that file has something like:
[Desktop Action NewPrivateWindow]
Name=Open a New Private Window
Name[ar]=افتح نافذة جديدة للتصفح الخاص
... many other languages...
Exec=firefox -private-window
In order to support the opening of new containers, we should implement: firefox -container <foo> and this is double, but how to have the list of containers? From which profile? Also: that file cannot be generated at runtime because firefox runs with user permission, but that file, often is 'own' by root and it comes from installed packages (ubuntu, debian etc).
Comment 4•9 years ago
|
||
Putting this at P3 for now, and we will evaluate whether we want this later.
Priority: -- → P3
Whiteboard: [domsecurity-backlog] → [domsecurity-backlog][usercontextId]
| Reporter | ||
Updated•9 years ago
|
Summary: adding the ability to open containers via the toolbar/dock → adding the ability to open containers via the taskbar jump list/dock
Comment 6•9 years ago
|
||
(In reply to Andrea Marchesini (:baku) from comment #3)
> Many questions: Which container/containers do we want to show there? I don't
> think we want to make the whole list of containers there.
>
> About linux, this seems quite impossible. That menu comes from the
> firefox.desktop file. On my computer it is in
> /usr/share/applications/firefox.desktop
>
> Now, that file has something like:
>
> [Desktop Action NewPrivateWindow]
> Name=Open a New Private Window
> Name[ar]=افتح نافذة جديدة للتصفح الخاص
> ... many other languages...
> Exec=firefox -private-window
>
> In order to support the opening of new containers, we should implement:
> firefox -container <foo> and this is double, but how to have the list of
> containers? From which profile?
On Windows I think we need to provide a "select container" chrome page here. The profile should be the default profile.
Containers are great, except that they are very hard to access. The file menu is rarely used and is hidden by default on Windows, fyi.
Updated•9 years ago
|
Whiteboard: [domsecurity-backlog][usercontextId] → [domsecurity-backlog3][usercontextId]
Comment 7•8 years ago
|
||
Bulk change per https://bugzilla.mozilla.org/show_bug.cgi?id=1401020
status-firefox57:
--- → fix-optional
Updated•3 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Attachment #9384539 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•