Closed
Bug 168072
Opened 23 years ago
Closed 22 years ago
Mozilla always displays "cannot find x" for typed URLs while a page is loading and where the .com is not included
Categories
(SeaMonkey :: Location Bar, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: ascaris1, Assigned: hewitt)
Details
Attachments
(1 file)
|
16.43 KB,
image/gif
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2a) Gecko/20020909
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2a) Gecko/20020909
While a page was loading, I decided that I wanted to go to cnn's web page, so I
typed "cnn" into the URL bar. Rather than go to www.cnn.com as it usually does,
Mozilla stops the page loading and simply replies "cannot find cnn". If I hit
enter on the URL bar again, the CNN page loads.
Obviously, the "cnn" typed url is not important; it simply is a good
demonstrator for this problem as it is short and easy to type.
Reproducible: Always
Steps to Reproduce:
1. Begin loading any web page.
2. While the page is loading, type "cnn" into the title bar (obliterating
whatever is there already) and hit enter.
Actual Results:
Stops loading the current page, and displays an alert box with "Cannot find cnn".
Expected Results:
Stopped loading the current page and attempted to resolve "cnn", which would
have then loaded www.cnn.com. Typing simply "cnn" works when a page is not
loading; it should work IMO if typed when a page is loading. IIRC, Netscape
4.79 did not have a problem with this.
| Reporter | ||
Comment 1•23 years ago
|
||
May be related to bug # 151499, if not identical to it. In both cases, the
problem occurs when a URL is typed without the .com at the end.
Comment 2•23 years ago
|
||
WFM with 2002113012/win2k/1.2.1
reporter (Frank): can you reproduce this bug with a recent build of mozilla (for
example, 1.2.1)? if so, please comment again with details. if not, please
resolve this bug as WORKSFORME. thanks.
| Reporter | ||
Comment 3•23 years ago
|
||
| Reporter | ||
Comment 4•23 years ago
|
||
Yes, I am still seeing this on recent builds. To reproduce this, load any page
via link or typed URL. Typing outpost.com works for this. Then, while
outpost.com is loading (obviously, this works better on a slow modem connection,
as I have), click on the URL bar and type "cnn" and hit enter. Mozilla responds
with "cannot find cnn" in an alert box, rather than trying to resolve cnn into
www.cnn.com. I will attach a screen capture image to illustrate.
Comment 5•22 years ago
|
||
Don't you have to hit CTRL or Alt or something to activate this now (since we
have keywords now?
| Reporter | ||
Comment 6•22 years ago
|
||
Jason,
I have all of the keywords and such disabled, as I always have, so when you type
"word" into the URL bar, Mozilla tries www.word.com.
I tried this again with the 20030619 1.4 branch build, and I was not able to
reproduce it. As per Michael's earlier instruction in comment #2, I am marking
this WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•17 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•