Closed
Bug 737
Opened 26 years ago
Closed 25 years ago
file:/// url navigation and generated directory
Categories
(Core :: Networking: File, defect, P1)
Tracking
()
M9
People
(Reporter: angus, Assigned: gagan)
References
Details
Bug report from Mathieu ARNOLD <arn@mygale.org>:
I put file:/c:/ into the location toolbar of viewer.exe
I clicked on Program Files
so, the location became : file://c:/Program Files
then i clicked on directx
and the location became : file://c:/directx which doesn't exist...
so the displayed page remained the same.
then i passed over 'Up to higher level directory' and the status bar
displayed file:/// which doesn't exist at all, so, i clicked on it, and
it crashed...
Reporter | ||
Comment 1•26 years ago
|
||
Adding original reporter to the CC list
Severity: normal → major
Priority: P2 → P1
Summary: Problems with file:/// url navigation and generated directory → ss:Crash with file:/// url navigation and generated directory
Comment 3•26 years ago
|
||
confirmed that file:// or file://c:/ causes a crash on win95 xpviewer 11/23a
build.
Updated•26 years ago
|
Summary: ss:Crash with file:/// url navigation and generated directory → problems with file:/// url navigation and generated directory
Comment 4•26 years ago
|
||
No longer crashing with 11/24 build on win95 xpviewer, but still some problems
with file navigation. Taking off stop ship list and changing summary.
The problems are still as angus noted. Gags, are you the person for this or
someone else?
There are other bugs too that relate to the way the url is displayed in the
location bar. Investigating...
file://C:/ URL works for HTML files (I have created a HTML file and I was able
to open with viewer.exe). It seems to have problems opening .txt files. I was
able to traverse the directories on the C: drive also.
I will keep trying to narrow down.
thanks,
raman
I put file:/c:/ into the location toolbar of viewer.exe
>I clicked on Program Files
>so, the location became : file://c:/Program Files
>then i clicked on directx
>and the location became : file://c:/directx which doesn't exist...
>so the displayed page remained the same.
The above still seems to happen. In 4.x, the URL was being escaped (adding %..)
and in 5.0 we don't seem to do that. That could be the cause of the problem.
thanks,
raman
Updated•26 years ago
|
Assignee: raman → gagan
Status: ASSIGNED → NEW
Comment 10•26 years ago
|
||
I thought raman is no longer working on netlib - giving back to gags.
Comment 11•26 years ago
|
||
setting paulmac as QA contact for all gagan's bugs (sorry for the spam)
Assignee | ||
Comment 12•26 years ago
|
||
Fixed with N2.
Updated•26 years ago
|
Target Milestone: M4 → M6
Comment 13•26 years ago
|
||
Netlib rewrite should take care of this
Assignee | ||
Comment 14•25 years ago
|
||
Per DP's suggestion marking these till M8. Though Necko lands with M7, we will
be able to verify it for M8.
Updated•25 years ago
|
Target Milestone: M8 → M9
Comment 15•25 years ago
|
||
Necko landing in M8, moving to M9
Comment 16•25 years ago
|
||
Necko landing in M8, moving to M9
Comment 17•25 years ago
|
||
Changing all Networking Library/Browser bugs to Networking-Core component for
Browser.
Occasionally, Bugzilla will burp and cause Verified bugs to reopen when I do
this in a bulk change. If this happens, I will fix. ;-)
Assignee | ||
Comment 18•25 years ago
|
||
Check with Necko please.
Summary: problems with file:/// url navigation and generated directory → NECKO: problems with file:/// url navigation and generated directory
Comment 19•25 years ago
|
||
this is a dup of another bug warren has
*** This bug has been marked as a duplicate of 6936 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 20•25 years ago
|
||
Bulk move of all Networking-Core (to be deleted component) bugs to new
Networking component.
Component: Networking → Networking: File
Summary: NECKO: problems with file:/// url navigation and generated directory → file:/// url navigation and generated directory
You need to log in
before you can comment on or make changes to this bug.
Description
•