Closed
Bug 179083
Opened 22 years ago
Closed 19 years ago
hot keying url from pegasus email causes number 1 to display in browser url window every time
Categories
(SeaMonkey :: Location Bar, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: jerry, Assigned: hewitt)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530 When there is a url address in a pegasus message, and I click on it, browser opens, but always puts a 1 in the URL window. Sometimes I can close browser and click a second time in pegasus message , and correct address will then show up in browser window. Reproducible: Always Steps to Reproduce: 1.click on url in pegasus message 2. 3. Actual Results: 1 showed up in browser url window Expected Results: put and connected to url as displayed in pegasus message window.
Comment 1•21 years ago
|
||
This is true with Pegasus 4.02a (latest version for Windoze) on Windows 2k (5.0.2195 sp 3 build 2195) with English as default language. Pegasus uses its own external program URLPROXY.EXE which I think uses very standard Windoze calls. It only happens if Mozilla isn't launched, if it is launched, everything goes fine so I assume something is happening in the parsing of a commmand line invocation of Mozilla that gets interpreted as a call to www.1.com if mozilla isn't running but either the "1" doesn't get passed or something else is different if URLPROXY.EXE is running. Politics: Pegasus are at www.pmail.com and, though in a sense they're competition and not open source, I do still have great indeptedness to them for years of cheap/free Emailing and don't want to change from them until I really can go open source for everything and be able to shift all my pegasus archives. Thanks for Mozilla and bugzilla: looking good so far.
Comment 2•21 years ago
|
||
*** Bug 197313 has been marked as a duplicate of this bug. ***
Comment 3•21 years ago
|
||
In a fit of total perversity, I decided to go ahead and upgrade form Pegasus 3.12c to 4.02a, since I was in a upgrading mood this night. Now I no longer get this behavior and everything is working fine. (It also worked fine in Pegasus 4.02 before I applied the 4.02a patch.) Can anyone else get this bug to happen with Mozilla 1.3 and Pegasus 4.02+. If not, then this bug should be marked RESOLVED WONTFIX with a note placed in the documentation for users of Pegasus to upgrade to the latest version of that program.
Comment 4•20 years ago
|
||
WFM, Mozilla 1.8a, Pegasus 4.21c. It has been working for a long time. Reporter, have you seen this bug lately? If not, we will mark this as resolved worksforme.
Comment 5•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 6•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•