totallymike
losses (form field data, tab history etc.) when sending pages from one Firefox container to another
For example: loss of the title of this issue, if I change/move/switch to a different container before submission.
Re: https://github.com/mozilla/testpilot-containers/wiki/Moving-between-containers and the nature of Firefox containers, I assume that such losses are unavoidable. So please consider adding an on-screen hint … maybe by default, once per Firefox session, a modal dialogue that will give the user the opportunity to Cancel a move before it's too late.
Or maybe refrain from closing the tab from the original context, and (after the copy is complete) offer a non-modal dialogue in the new context.
Side note: https://github.com/kesselborn/conex/issues/8
… refrain from closing the tab from the original context, and (after the copy is complete) offer a non-modal dialogue in the new context.
Maybe think of that (dialogue) as a complement to the Control key approach. Like, a dialogue if the first change of context during a session is without Control key modification.
… I assume that such losses are unavoidable. …
Was that a false assumption?
From What is (and isn't) separated between Containers under Security/Contextual Identity Project/Containers - MozillaWiki:
Not separated by Containers (On Purpose):
- Saved Passwords
- Saved Search and Form data
- …
Something like a warning the very first time you switch contexts probably makes sense.
The extension doesn't really inform you that it's straight up destroying the old tab and creating a new one in a different context.
I don't think I'd like to have the warning show up more frequently than that. I'd get sick of it pretty quickly :)
FWIW from Drawings for Firefox containers under Drawing user stories as cartoons - Lounge - Open Source Design (and via https://twitter.com/grahamperrin/status/917100338255138818):
… A comical demonstration of something lost through movement, maybe …
Frankly, I'm not sure what I'd want to do about on-page form data and such. I feel like that's probably out of scope for this add-on since there's just about no way to preserve live data for every page everywhere that I can think of.
The one thing, I think, that bums me out more than possibly losing half-filled-out Form data, is the back button. When starting this addon, I almost scrapped it all together as not being worth it when I found out I'd lose the back button history!
Yeah. I never expected this extension to do what Firefox can not (or should not).
On one hand: it's for Mozilla, more than any other group or individual, to manage user expectations – including bum-outs and thoughts of scrap – around its container technology. On the other hand: as Mozilla positively encourages open design, so anyone might come up great ways of conveying what's great, good and not good about Firefox containers.
@girliemac through your popularity and skills you're invited :-) but no pressure.
Food for thought.
Before and after. The tree on the right is identical to the tree on the left:
The container is different.
;-)
The wish is neither to discourage getting people on board as users of containers, nor to get users off.
The wish is … I guess, for light-hearted education that:
- with a change of container, you might sometimes not get everything that you want.
Credit for the original photographs: Hammers and High Heels: Green and Gold to Go With the Stars & Snow! It's Our 2013 Christmas Tree!
Mozilla's on-boarding images for Multi-Account Containers are at https://github.com/mozilla/multi-account-containers/tree/master/webextension/img
The horizontal flip, and the lazy, flippant pastes, are down to me.
The decorated (Christmas) tree metaphor, thoughts of which formed around a month ago, was partly behind the word Pottery, which I threw in whilst beginning to kick the ball around before a rename of Taborama. Something relatively rich and adorable in a pot, where a pot is a type of container. Certainly a weird idea two weeks ago (without the background thoughts) … probably no less weird now :-) with the lazy visual mock-up above, which is not entirely what I had in mind a month ago.