[Bug]Private start with command line ruins tabs list in normal

[A Former User]

A Former User last edited by

for fast use of private window i created myself a link file
D:\Progs\Opera\launcher.exe --private

• if you run normal Opera with tabs list you use and then private with this link file - everything is ok.
• if normal is closed and you run private, then close private and run normal - everything is fine too.
• if normal is closed and you run private, then while private is still open run normal - all your tabs in normal are gone! whatever run/close patterns you do next, tabs are already gone.

hope this helps to fix. lost my tabs already twice to figure this out.

[burnout426]

burnout426 Volunteer last edited by

Confirmed. Worth filing a bug report.

I see that if you launch Opera normally, open a private window, close the normal window so that only the private window is open and launch Opera normally, a non-private window opens with the tabs from last time with no problems. So, it's just with the command-line setting it seems.

[mryanmarkryan2]

mryanmarkryan2 last edited by

Are you running the launcher or directly to the exe?

Have you fscked your local propeller head today?

[burnout426]

burnout426 Volunteer @mryanmarkryan2 last edited by

@mryanmarkryan2 I was running launcher.exe and from OP's post, it looks like launcher also. If launcher.exe is forwarding the --private correctly, I would assume it wouldn't matter.

[mryanmarkryan2]

mryanmarkryan2 @burnout426 last edited by

@burnout426
Just curious if you got the same result running the app directly.

Have you fscked your local propeller head today?

[burnout426]

burnout426 Volunteer @mryanmarkryan2 last edited by

@mryanmarkryan2 Gotcha. I can check.

[burnout426]

burnout426 Volunteer @mryanmarkryan2 last edited by

@mryanmarkryan2 said in [Bug]Private start with command line ruins tabs list in normal:

Just curious if you got the same result running the app directly.

Yes. Same result.