Closed Bug 139736 Opened 22 years ago Closed 22 years ago

URL disappears or is not refreshed in the URL bar

Categories

(SeaMonkey :: Location Bar, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: lauriemann, Assigned: hewitt)

Details

This is a very erratic bug, but as a person who frequently copies and
pastes URLs from the URL bar, it's EXTREMELY FRUSTRATING.

Sometimes, the URL disappears altogether.

Sometimes, an old URL appears while a completely different page is
being displayed.

This bug is annoying enough that I have to go back to Netscape 6.2.
Also seeing this under Win2K, RC1.2, build ID 2002051006 - got it when I
launched Navigator from Mail&Newsgroups window; no URLs appeared in location bar
at all. Launched another Navigator window (this time from first Nav window),
URLs came back.
Perhaps this is related/a dupe of bug 115961?

I've just added a comment to that bug describing my blank URL bar experience
with trunk build 2002053104 on Win98, however did not see anything appear
spontaneously in the bar as seems to be implied by the reporter's description here.
I have a similar problem when using tabs. Open two tabs. Go to an url which
doesn't exist, www.solihsjfduij.do, wait until Moz shows the (irritating) site
not found dialog. Then switch tabs and switch back. Result: url gone. Not good,
because if I mistype the url, say www.mozillla.org, the url is gone and when
using tabs for browsing news-sites and opening the related stories in a
background tab. If the url doesn't exist, there is no way of knowing which url
it is that doesn't exist, because it disappeared.
Can you reproduce on a current build ? I have not seen the non-tabbed browsing
case happen for a long time.
No response from reporter...
Closing as WFM.

Reporter if you think this is still a problem please file a new bug after
testing with a recent build.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.