implement ui for creating new container about conex HOT 7 CLOSED

Quick & Dirty idea: Just make a button that open a new tab to : about:preferences#containers . That'll let you create / edit containers now and will likely continue to evolve as Mozilla adds more features.

from conex.

Yeah, that was my idea as welk, but it’s not possible to do that :( ... I guess for security reasons

from conex.

@grahamperrin my only guess it that it would potentially cause some really nasty security issues (opening preferences in a hidden iframe and change settings via js somehow? ... don't know -- it's really complex).
As to the alternative: the logic for creating, editing and deleting containers is super simple, I only lack the UI skills :'( -- or rather: I am really bad at it. If somebody can help, I am happy to integrate it. My only constraints are not to use any framework (just plain es6 and css).

from conex.

@kesselborn I'm interested in the reasoning for why this should be implemented. I feel like, if the user installs conex, they probably know how to manage containers already; why not just let them do it that way? In my last month or two of using conex, I've never felt like I didn't know how to create a new container or that it was too much work to do so.

from conex.

Yeah, without hesitation, first and foremost,

about:preferences#containers

Yes, it's quick and (I think) not a dirty idea.

If by Mozilla's design, an extension can not draw attention to a Mozilla-provided GUI to a preference that's integral to Firefox, that's insane less than sane. Actually, don't strike that, stet. From an end user point of view it is insane and I might want to bang my stetting head against a stetting brick wall.

Alternatively

Is it possible for an extension to do these two things?

1. set 2 for privacy.userContext.longPressBehavior
2. educate the user that pressing (not clicking) the ➕ icon, for a new tab, will present Mozilla's Manage containers menu option

from conex.

👍 from me = ideally I should set aside time to gain a non-developer understanding of the overlaps/conflicts between (a) privacy/security best practices and (b) WebExtensions APIs.

Realistically any such time is radioactively eaten by the broad fallout from the rundown to Firefox 57 😆 I'll stop myself there.

from conex.

this is done in >0.6.3

from conex.