Open
Bug 1288504
Opened 9 years ago
Updated 9 months ago
Customize about:newtab per Container
Categories
(Core :: DOM: Security, enhancement, P3)
Core
DOM: Security
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox57 | --- | fix-optional |
People
(Reporter: tanvi, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: [userContextId][domsecurity-backlog2])
Attachments
(2 files)
In about:newtab, show me history from the specific container I'm in, rather than history from other containers. This will help prevent me from making a mistake and visiting the wrong site in the wrong container.
Potentially even add some text to the about:newtab page that talks about containers or links to containers help pages. Ex: here's an old UI mockup - https://wiki.mozilla.org/File:Containers-start-page.png. I'm not proposing we do this, but we can integrate some text into the existing about:newtab page. Bram, can you make a new mockup?
Reporter | ||
Updated•9 years ago
|
Flags: needinfo?(bram)
Updated•9 years ago
|
Priority: P2 → P3
Whiteboard: [userContextId][domsecurity-backlog] → [userContextId][domsecurity-backlog2]
Reporter | ||
Updated•9 years ago
|
Priority: P3 → P2
Comment 1•9 years ago
|
||
Flags: needinfo?(bram)
Comment 2•9 years ago
|
||
Here, and above, are simple examples of how the new tab page can have different headings depending on the container it’s currently in.
Hello,
I'm the author of the duplicated bug (#1335706)
now, when click on the '+' to open a new tab or use "new tab" keyboard shortcut, it open a new tab wit no container.
I'll find handy that have this page page can display pinned site already associated with it's container perhaps using visual hints (container name + color) of the associated container .
Updated•8 years ago
|
Priority: P2 → P3
Comment 5•7 years ago
|
||
Bulk change per https://bugzilla.mozilla.org/show_bug.cgi?id=1401020
status-firefox57:
--- → fix-optional
Updated•2 years ago
|
Severity: normal → S3
Updated•9 months ago
|
Type: defect → enhancement
You need to log in
before you can comment on or make changes to this bug.
Description
•