Closed
Bug 168953
Opened 22 years ago
Closed 22 years ago
Crashes IMMEDIATELY on Typing "w" in Location Bar
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: lgschmidt, Assigned: asa)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020915 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020915 Trying to type a location in the URL/address/location bar, the moment I strike the "w" key, Mozilla immediately crashes, every time. Reproducible: Always Steps to Reproduce: 1.Highlight current location 2. strike "w" 3. Actual Results: crash
Comment 1•22 years ago
|
||
Maybe there's somehgting wrong with one of the earlier items in the lcoation bar. Try clearing it (see Preferences | Navigator | History) ...
Reporter | ||
Comment 2•22 years ago
|
||
"Maybe there's somehgting wrong with one of the earlier items in the lcoation bar. Try clearing it (see Preferences | Navigator | History) ..." Interesting - this actually leads to ANOTHER problem: the Preferences dialog pops up, but is FROZEN with Navigator selected and expanded; clicking on anything else on the left side of this box does nothing - only the OK/Cancel buttons work on the right side and the radio buttons and check boxes, but NOT the left side navigation panel!
Comment 3•22 years ago
|
||
Reporter, did you install the new build over a previous install? Make sure you make a clean install. Also, remove any files in your profile \chrome folder. Please report back.
Severity: normal → critical
Reporter | ||
Comment 4•22 years ago
|
||
David, Yes, I had installed over a previous version, so I did a clean install AND cleared the history - things seem to be fine now - THANKS! Larry
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 6•22 years ago
|
||
-> INVALID
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → INVALID
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•