Re:Microsoft Edge records browsing history in InPrivate mode
by madeofpalk on Monday February 01, 2016 @05:06AM
(#11010844)
Incorrect.
Chrome has support for profiles and having multiple open at the same time http://imgur.com/GU33K43
Best of all, they're persistent, making them ideal to have distinct 'home' and 'work' profiles in Chrome.
Re:Microsoft Edge records browsing history in InPrivate mode
by mattmanser on Monday February 01, 2016 @06:19AM
(#11011095)
And you can even create one for every client, I've got 5 profiles on the go at the moment.
Re:Microsoft Edge records browsing history in InPrivate mode
by dspillett on Monday February 01, 2016 @08:04AM
(#11011483)
Fairy nuf. I'll have to have a play with that. "File | New Session" is still probably more convenient for ad-hoc tasks though.
Re:Microsoft Edge records browsing history in InPrivate mode
by noja on Monday February 01, 2016 @04:53AM
(#11010789)
Firefox has been able to do this forever. It's called profiles. Start firefox with --ProfileManager to try it.
Re:Microsoft Edge records browsing history in InPrivate mode
by bratch on Monday February 01, 2016 @06:21AM
(#11011106)
Note that if Firefox is already running, you'll need to use --no-remote --ProfileManager. Details in WONTFIXed https://bugzilla.mozilla.org/show_bug.cgi?id=99828.
Re:Microsoft Edge records browsing history in InPrivate mode
by dspillett on Monday February 01, 2016 @08:06AM
(#11011497)
Fairy nuf. But that isn't nearly as convenient as "File | New Session" for ad-hoc tasks. And I thought only one profile could be in use at once in FF (though that could be worked around with multiple OS users) - am I completely barking up the wrong tree there or is that something that has changed in recent years?
It is one of the few things IE gets better (and has for a long time) than Chrome or Firefox where a single OS-level user can have at most two distinct sessions at any given time: one private and one not. It can be very handy from a development PoV when testing multi-user workflows in your application.
One caveat: if the site/application uses saved cookies rather then those set to expire at the end of the current session they will still interfere with each other when opened this way as saved cookies (those with an explicit expiry date/time) are considered global (with respect to the OS user) rather than local to the browser session.
I've not checked if this feature has carried into Edge. The clients I support are so backward that I'll not need to test against that this decade!