Closed
Bug 44261
Opened 24 years ago
Closed 24 years ago
Bad links act weird in html loaded from a file: url.
Categories
(Core :: Networking: File, defect, P3)
Core
Networking: File
Tracking
()
mozilla0.9.1
People
(Reporter: stephe, Assigned: dougt)
References
Details
(Keywords: hang)
Attachments
(1 file)
278 bytes,
text/html
|
Details |
If you load an html page from disk that has a link like:
<a href="relref.html">Relative</a>
where relref.html does not exist, an "Unknown File Type" dialog pops up that
says "You are about to download a file of type text/html." and "You can save it
or open it....", etc.
What is even worse is if you have a link like:
<a href="/absref.html">Absolute</a>
where you have an absolute path to a non-existent file, Mozilla runs for a while
(spinning barber pole) and the then freezes for a while (non-responsive UI,
won't repaint itself, etc.) before putting up the "Unknown File Type" dialog.
To reproduce, save the attachment to disk and load it in Mozilla. Click on
Relative to get the first behavior. Clock on Absolute to get the freezing.
This is happening on the latest nightly Mozilla build, 2000062820.
Reporter | ||
Comment 1•24 years ago
|
||
Comment 2•24 years ago
|
||
unable to reproduce this with 062914 build on NT or win2K (also tested on Mac
OS 9 for good measure). I'm resolving this worksforme. Reporter, what build
did you see this? If you still see it on current builds after a clean install
please re-open. Thanks for your help in testing mozilla and reporting bugs.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 3•24 years ago
|
||
I am seeing the exact same behavior I reported using a clean install of 062920
on NT4. Remember that the attached html page has to be loaded from disk for
this to happen. I also tried this on Linux, and there I see a bogus ftp-like
directory listing. In both cases I would expect the NN4 behavior which simply
put up a dialog that said "Unable to find the file or directory."
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 4•24 years ago
|
||
OK, I see this with 063008 mozilla build on NT. This is Networking.
Assignee: asa → gagan,ruslan
Status: UNCONFIRMED → NEW
Component: Browser-General → Networking
Ever confirmed: true
QA Contact: doronr → tever
I'll look into it.
Per PDT mtg with gagan, moving from [nsbeta2+] to [nsbeta2-]
Whiteboard: [nsbeta2+] → [nsbeta2-]
Comment 10•24 years ago
|
||
Nominating for nsbeta3. Web authors are quite likely to encounter this bug when
working on the local versions of Web sites. See also bug 45144.
Comment 12•24 years ago
|
||
->WORKSFORME (Linux build 2000100909)
Reporter, please re-verify against latest build.
I tried the testcase, and in both cases I got the expected error
message: Not Found!
Status: NEW → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 13•24 years ago
|
||
You are saving the html page to disk and loading it from there, right? On
Mozilla 100904 on NT4, I no longer get the bogus Unknown File Type dialog or the
freezing. I do, however, get no message whatsoever. Mozilla thinks a while and
then displays a blank page. The status bar says "Document Done". Mozilla says
nothing about the page not existing. I will try Linux tonight and see how that
is behaving.
Reporter | ||
Updated•24 years ago
|
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Reporter | ||
Comment 14•24 years ago
|
||
Mozilla 100908 on Linux behaves exactly as I described for NT4 in my previous
comment. I am, therefore, reopening the bug even though Mozilla behaves much
better than it did before, but still Mozilla should work like NN4 in this case
and put up a dialog saying "Unknown file or directory."
Comment 15•24 years ago
|
||
Ok, I am seeing this bug now. As you later describe, the
behavior is that Mozilla just says Document Done and shows
a blank page. This actually seems to be the behavior whenever
a local resource/file is not found. It makes sense that we
would not see this problem for http: since the server sends
us the "Not Found" page. We need to have a similar response
generated locally when a file: (or for that matter a resource:)
fails to locate the URL.
Comment 16•24 years ago
|
||
The freeze with href="/stuff" or src="/stuff" links from file urls is bug 38643.
Assignee: gagan → dougt
Status: REOPENED → NEW
Target Milestone: M18 → mozilla0.9.1
Comment 17•24 years ago
|
||
->dougt
Assignee | ||
Updated•24 years ago
|
Comment 18•24 years ago
|
||
*** Bug 71081 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 19•24 years ago
|
||
maybe related to 64668
Assignee | ||
Comment 20•24 years ago
|
||
It sounds like now this bug is that we are not presenting the user with an
dialog that states "file not found". I am sure that there is a duplication of
this floating around...
Assignee | ||
Comment 21•24 years ago
|
||
*** This bug has been marked as a duplicate of 78738 ***
Status: NEW → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•