Open
Bug 1295750
Opened 8 years ago
Updated 2 years ago
integrating disposable/one-shot containers into DevTools
Categories
(Core :: DOM: Security, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox51 | --- | affected |
firefox57 | --- | fix-optional |
People
(Reporter: kjozwiak, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [userContextId][domsecurity-backlog])
Several users have requested the ability to create disposable/one-shot containers. As the request is tailored for more advanced users, Bram suggested adding the capability into DevTools.
(Bram Pitoyo [:bram] from bug#1283314comment#7)
> One way that I think containers can integrate within DevTools is via an icon
> that says “Open page in a new container tab”.
>
> It does exactly what it says on the tin, except we’ll open a disposable
> container that will delete itself when closed and does not have the ability
> to replicate (ie. there’s no way to open another container tab of the same
> type).
>
> Thoughts? Maybe we should move all the DevTools integration design and
> discussion into another issue. I do think that containers and DevEdition is
> a perfect fit.
Comment 1•8 years ago
|
||
Here are a couple more devtools / container ideas we discussed at the devtools meeting this week:
* Storage inspector integration - manage cookie jars through the devtools storage UI as a way to avoid needing to either edit cookies directly or manage multiple browser processes
** Use case 1: Test security on a page by reloading it after 'deleting' all of the cookies (i.e. switching to a new container), but being able to restore them easily
** Use case 2: Manage multiple logins for development (one tab as admin user, one tab as normal user)
* Show the color of the active container somewhere in the toolbox
Updated•8 years ago
|
Priority: -- → P3
Comment 2•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
You need to log in
before you can comment on or make changes to this bug.
Description
•