Closed
Bug 40063
Opened 25 years ago
Closed 25 years ago
file:/ browsing breaks history
Categories
(Core :: DOM: Navigation, defect, P3)
Core
DOM: Navigation
Tracking
()
VERIFIED
FIXED
People
(Reporter: jmd, Assigned: rpotts)
References
Details
(Keywords: relnote)
go to a file URL, say 'file:///foo/bar'
double click a directory to enter it, say 'images'
double click another directory to enter it, say 'testing'
double click a FILE to open it, say 'test.jpg'
Now, by the above, you should have four history entries. Well, you do.
Unfortunatly, all four entries are for:
file:///foo/bar/images/testing/test.jpg
this is related to another bug, history entries for directories aren't being
named. Also, if you don't eventually open a file, the history entry remains
blank, and 'back' will show you the current directory, unstead of the last.
| Reporter | ||
Comment 1•25 years ago
|
||
The blank problem is bug 38504. I'm not sure which is blocking which, so I won't
mark anything.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → M17
Comment 3•25 years ago
|
||
cc'ing waterson.
This bug happens because,after a directory is viewed, clicking in a file or
a sub-directory replaces the current url in the page instead of going thro'
browserAppCore's loadUrl(). Basically some call to window.content.location.url =
<...> s'd be replaced with a call to browserAppCore.loadURL(). can you point me
to where this is done?
Comment 4•25 years ago
|
||
The magic happens in nsDirectoryViewerFactory::CreateInstance(), here:
http://lxr.mozilla.org/mozilla/source/xpfe/components/directory/nsDirectoryViewer.cpp#1429
Comment 5•25 years ago
|
||
Chris,
Obviously you understand directoryViewer better than I do. I thought this w'd be
a simple fix in a JS file. The problem is what I have described above. I think
you can fix this faster than I can.
Thanks,
Assignee: radha → waterson
Status: ASSIGNED → NEW
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M17 → M19
Comment 6•25 years ago
|
||
yep, I'm seeing this too, linux.
Comment 8•25 years ago
|
||
nsDirectoryViewerFactory::CreateInstance() just gets called to create a content
viewer for the "http-index-format" mimetype, right?. Perhaps session history
support probably needs to be added for the case when a content viewer is created
in the webshell.
Radha, since you know how to add support for session history in JS, perhaps you
can better decide where to add in similiar support via native code in the
appropriate spot.
Assignee: rjc → radha
| Reporter | ||
Comment 9•25 years ago
|
||
adding relnote, to go along with the ftp:// history bug which is relnote'd
Keywords: relnote
Comment 10•25 years ago
|
||
I don't know much about contentviewer creation etc.. and the way it is done in
teh directory viewer. I think rick potts will understand this better.
Assignee: radha → rpotts
Comment 11•25 years ago
|
||
*** Bug 45120 has been marked as a duplicate of this bug. ***
Comment 12•25 years ago
|
||
*** Bug 46894 has been marked as a duplicate of this bug. ***
Comment 13•25 years ago
|
||
*** Bug 47337 has been marked as a duplicate of this bug. ***
Comment 14•25 years ago
|
||
*** Bug 40537 has been marked as a duplicate of this bug. ***
Comment 15•25 years ago
|
||
*** Bug 47339 has been marked as a duplicate of this bug. ***
Comment 16•25 years ago
|
||
changing platform to ALL adding nsbeta3 keyword
Keywords: nsbeta3
Hardware: PC → All
Comment 17•25 years ago
|
||
in case some triage team somewhere doubts, this bug was reproduced in a recent build - "Problem still exists in 2000080108
linux." -
darkskyz@cyberspace.org
Comment 18•25 years ago
|
||
I can't reproduce this in today's build. Entries are made for each of the
sub-directories/files visited. However the back/forward/go menu items look
blank. That is a different problem. But you can go back and forward properly in
marking fixed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 19•25 years ago
|
||
looking at the 2000082108 builds this seems to work beautifully now...marking VERIFIED
Status: RESOLVED → VERIFIED
Component: History: Session → Document Navigation
QA Contact: claudius → docshell
You need to log in
before you can comment on or make changes to this bug.
Description
•