294216 - no redirection when choosing a link (for example google search hits) after disabling chatzilla

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Improver]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.8) Gecko/20050511
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.7.8) Gecko/20050511

the aim is to use a differnt irc client than chatzilla:
when disabling chatzilla, mozilla isn't able to use links in webpages. No matter
if you try google search results or different links on other pages. no action
when "clicking" on links. 
Typing of URLs is recognized and leads to connecting to the URL. Links let the
browser freeze. When closing it, the mozilla service/app stays in the
taskmanager and the process has to be killed manually.

The following procedure is taken, to disable chatzilla :

1. Shutting down Mozilla
2a. Renaming of the files components/chatzilla-service.js and
chrome/chatzilla.jar
 or 
2b. moving the above files away/deleting (I tried both methods)
3. Runing regchrome

After doing so, mozilla is able to catch irc links and opens them with a desired
irc client. 

Please provide a possibilty to disable chatzilla or at least to have the
possibilty to choose an application for IRC.

kind regards

Improver

Reproducible: Always

Steps to Reproduce:
1. disabbling following files:
components/chatzilla-service.js and chrome/chatzilla.jar
2. starting mozilla
3. choosing a search result on google
Actual Results:  
-no forwarding

-freezing, but no crashing -> closing the app, because nothing happens.

Expected Results:  
- direct tom the link

Comment 1

[OstGote!]

Can't you install Mozilla without Chatzilla and use other IRC clients?

Comment 2

[Boris Zbarsky [:bzbarsky]]

> 1. disabbling following files:

How exactly?

Comment 3

[:Gijs (he/him)]

You should just not install ChatZilla at all, or set the external protocol handler pref for irc. If you mess with the chrome stuff yourself, AND deliberately run regchrome again, I don't see how you can complain that things break (though I'm unable to reproduce in the first place.

Lack of info (comment #2), deliberately screwing over the files that the app uses --> INVALID