Closed Bug 197313 Opened 23 years ago Closed 23 years ago

Quirky behavior when Mozilla is invoked from Pegasus Mail

Categories

(SeaMonkey :: General, defect)

x86
Windows 98
defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 179083

People

(Reporter: ernestcline, Assigned: asa)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; T312461) Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 I do not have (nor want) Quick Launch enabled. I do have Mozilla enabled as my default web-browser and Pegasus Mail as my default mail client. When I double click on an http reference in an e-mail and Mozilla is not already active, Mozilla displays some quirky behavior as described in the Actual Results section. Reproducible: Sometimes Steps to Reproduce: 1. Have Mozilla closed and Quick Launch disabled 2. Open Pegasus Mail 3. Double-click on an http: address in an email. Actual Results: I have observed three seperate behavors. One is the expected behavior. Another is the that page loads in a new window, but the URL that is displayed is "1". Mozilla then tries to load "1", showing the status message "Connecting to 1..." Eventually, it gives up and gives the alert message "The operation timed out when connecting to 1." The window then works normally. The third is similar, except that the page is loaded into a new window with the URL not displayed, and a second window is created where Mozilla tries to open 1. The window with the blank URL works excepet that the URL is never displayed even when another window is loaded via a click on that web page. I can't remember if a new URL can be typed in or not and I haven't been able to duplicate this behavior since I decided to file bug report. Expected Results: Open a single new window with the specified address. I use Pegasus Mail v3.12c (Win32). This sounds very similar to Bug 166872 except that in that bug, the desired content doesn't get rendered, making it a Major problem instead of the Trivial problem that it is for me.
Duplicate of bug 179083?
Just got Mozilla 1.3. Same behavior occurs.
Yeah, I'd say its a duplicate. I am also posting a comment in Bug 166872 about Bug 179083. *** This bug has been marked as a duplicate of 179083 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.