Portable builds still interfere with install builds

[Tomaso]

The portable builds still interfere with install builds, even without the semicolon in front of MOZ_NO_REMOTE=1 in Palemoon-Portable.ini.

How to reproduce:
1) Make sure that you've got PM installed, but not running, under Windows.
2) Launch a portable PM build.
3) In the taskbar, right-click on the portable build and choose 'Open new tab', 'Open new window' or 'New private window'. [*][/b]
4) Close the portable build.
5) Launch the installed PM version..
It will now run a compatibility check for add-ons!

(Tested with PM v26.5.0,x64 and PM Portable v27.0.0.b3,x64 under Win8.1)

[*][/b] For the portable builds, there also seems to be bug when selecting 'Open new tab' from the taskbar..
It opens a new window instead.

[Moonchild]

Windows jumplists are rather fickle -- it's obviously been launching a non-portable browser window by choosing that. I'll have to see if I can disable those in the portable.

In the palemoon-portable,ini, under the user preferences header, add:

Code: Select all

;(disable jumplists)
browser.taskbar.lists.enabled=false

That should disable jumplists permanently (which won't properly work on a portable anyway as you've seen).

[Tomaso]

In the palemoon-portable,ini, under the user preferences header, add:

Code: Select all

;(disable jumplists)
browser.taskbar.lists.enabled=false

That didn't help any.
The menu is still there, and using it has got the same effect as before.

[Moonchild]

Did you test this on a fresh install of the portable?

[Tomaso]

Did you test this on a fresh install of the portable?

I did right now, and it works.
The menu items are gone! :)
Will this entry be included for the portables by default from now on?

--

EDIT:

it's obviously been launching a non-portable browser window by choosing that.

Actually, no.
It launched a new portable window.

[Moonchild]

It can't have been a portable window if it interfered with your installed profile. SO, it likely called palemoon.exe directly which doesn't have the profile parameter, as a new process (which also explains the new window instead of a new tab).

[Tomaso]

It can't have been a portable window if it interfered with your installed profile.

Really, I've tripple-checked this now!:
1) Made sure that v26.5.0,x64 install build wasn't running.
2) Launched the portable build v27.0.0.b3,x64.
3) Right-clicked on its entry in the taskbar and choose 'Open new tab'..
This opens a new window for v27.0.0.b3,x64 portable!
4) Closed v27.0.0.b3,x64 portable.
5) Launched v26.5.0,x64 install build..
It then runs a compatibility check for add-ons!
Happens every time.