On Tue, 07 Apr 2015 03:59:40 +0200, Steve Hayes
wrote:

On Mon, 06 Apr 2015 09:36:42 -0500, Char Jackson
wrote:

On Mon, 06 Apr 2015 02:47:43 +0100, choro wrote:

After I reported problem solved, it came back with a vengeance only a
few hours later. Forget about it not responding AFTER I had turned
Firefox off, Firefox (latest edition) refused to open any URL from
newsgroups EVEN WHILE it was up and running.

If I fill in the missing pieces of the story, is it safe to assume that
Firefox is working perfectly well for you in every way EXCEPT integration
with your Usenet newsreader?

If so, it doesn't sound like a Firefox issue at all.

Firefox, being open source, and perhaps be updated by people who use
different newsreaders etc, and its behaviour varies from one update to
the next.

If I click on a URL in an e-mail message or newsgroup , various things
can happen.

1. It loads Firefox and opens the page (rare).
2. It loads two instances of Firefox, one with a blank page and the
other with the page requested (most common).
3. Nothing. You have to have Firefox already running before it will
open a URL.
4. Even if Firefox is already running, it won't open the URL. You have
to copy it and paste it into Firefox to achieve that.

No sooner does an update come along that behaves as in (1) than
someone "fixes" it so that it behaves in one of the other ways.

In the years that I've used browsers, whether it be early versions of IE,
Netscape, Firefox, what have you, I have only encountered two behaviors:

1. If the default browser is already running, the URL that I clicked will
cause a new window (or a new tab, if the browser supports tabs, as Firefox
does), to open at that address. Always repeatable and predictable.

2. If the default browser is not running, clicking a URL will cause the
default browser to launch to the URL that I clicked. Again, this behavior is
totally repeatable and predictable.

I've never seen any of the other behaviors listed above, going all the way
back to long before Firefox was developed.

If it helps, this is my current browser launch string, as configured in
Agent:
C:\Program Files (x86)\Mozilla Firefox\firefox.exe "%1"

The weird behaviors described above appear to indicate that the browser
launch string is misconfigured in some way.

--

Char Jackson