Closed Bug 147874 Opened 23 years ago Closed 23 years ago

entering url in url bar does not change location

Categories

(SeaMonkey :: Location Bar, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 90337

People

(Reporter: sean_kirkpatrick, Assigned: hewitt)

Details

RC3: My browser defaults to an internal company website. If I select the text in the URL field and enter a new URL (http://www.cnn.com, for example), the browser fails to connect to the specified site and remains on the current site. If I use the dropdown box and select some place that I've already been, the browser takes me there just fine. This is different behavior than RC2.
I experienced this exact problem intermittently in RC1 and RC2. It is very frustrating since you have to use CTRL+SHIFT+L to open the location dialog to get anywhere. All open windows seem to suffer from it at the same time, or not at all. It's hard to say why this occurs.
Yeah, happens to me too. Always seems to happen the first time I first start up my browser, then never again
I have been running 1.0 on my G4 desktop, OS 9.2, since June and this only happened to me occasionally, but it has become more frequent. I often found when I had trouble with it that there was a contextual menu that had popped up behind my browser window, and after "releasing" it (usually by choosing View Page Source because I couldn't get it to close on its own) the bar would start working again. I have been using Netscape 6 on my Powerbook G3, OS 9.2, at home and just started having the same problem (location bar not working) but there is no contextual menu open in the background (visible at least.) It started out intermittent but has increased. Just 2 days ago I downloaded Mozilla 1.0 to use instead of Netscape 6 on my PB because it was getting to be a pretty frequent problem. Unfortunately Mozilla is exhibiting the same behavior -- I can't use my location bar at all, even after rebooting Mozilla, and restarting my machine. It leads me to believe that there's some shared resource between the two that's causing the problem... I hope this helps.
*** This bug has been marked as a duplicate of 90337 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.