212512 - Enable profile manager to use running instances when it detects a locked profile (using xremote, ...)

Status: NEW

(SeaMonkey :: Startup & Profiles, enhancement)

Description

[Steven T. Hatton]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030709
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030709

When I try to view the help for TurboXML
(http://www.tibco.com/solutions/products/extensibility/turbo_xml.jsp) it trys to
launch a new browser session rather than calling mozilla -remote "openurl(<uri
to help files>)".  That means when I try to view the help, I either use a
different profile than the one I have running (Yes, I always have Mozilla
running!), or I have to exit Mozilla, and use TurboXML to launch a new session.
 I'm sure TurboXML could (should) be fixed, but this is not unique to this
application.  It would be nice if there were a button on the profile manager to
tell it to translate the launch command issued by TurboXML into a -remote call
to the existing instance.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Boris Zbarsky [:bzbarsky]]

See also bug 122698 (this bug is not a duplicate of that one; they're different
ways of accomplishing the same goal).

Comment 2

[Tim]

Tweaked summary.

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 6

[Karsten Düsterloh]

Still a valid enhancement request.