Closed
Bug 1513794
Opened 6 years ago
Closed 6 years ago
Nightly process is targeted weirdly when called as default browser
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: contact, Unassigned)
Details
Attachments
(1 file)
139.16 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0
Steps to reproduce:
I have regular Firefox installed, and also Nightly, set as default browser in my OS (Windows 10).
I have a profile dedicated to each Firefox version, and use " -p myProfile -no-remote" to be able launching each Firefox indenpendantly.
If I launch an instance of Nightly, when I open a link from another software (ex: Thunderbird, Discord), this software can't be able to use the existing Nightly process and create a new one. However, this new process is accessible to others soft.
Use case example:
- I launch Nightly and browser the net
- I open a link in a mail from Thunderbird: new Nightly process is create
- I open a link from Discord: it's opening in the Nightly process from Thunderbird
I attached a scheme in this issue to get more visual explanations.
Actual results:
Nightly process isn't accessible by other softwares when launched by user, but it is when launched from a software.
Expected results:
Nightly process should be accessible by any place.
Summary: Nightly process is target weirdly when called as default browser → Nightly process is targeted weirdly when called as default browser
Hi,
Thanks for reporting this issue. Are you seeing this issue with release or Beta builds of Firefox being the default browser?
Component: Untriaged → Startup and Profile System
Flags: needinfo?(contact)
Product: Firefox → Toolkit
With the Release Firefox as default browser, it works perfectly. I haven't try with Beta, 'can do that in the next few days.
Flags: needinfo?(contact)
I guess that with this news : https://support.mozilla.org/fr/kb/dedicated-profiles-firefox-installation this issue could be closed soon.
Comment 4•6 years ago
|
||
(In reply to contact from comment #0)
Actual results:
Nightly process isn't accessible by other softwares when launched by user
This is the expected behavior when launching with -no-remote.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•