Closed Bug 14980 Opened 25 years ago Closed 16 years ago

Directory list state does not persist when returning to it from a local webpage

Categories

(SeaMonkey :: UI Design, defect, P3)

x86
Windows 95
defect

Tracking

(Not tracked)

RESOLVED INVALID
Future

People

(Reporter: bugs, Assigned: jag+mozilla)

Details

Steps to reproduce:

1) load a local folder by typing in a file:// URL (e.g. file:///c|/)
2) navigate through your local directory tree, and find a webpage or other file
viewable by Mozilla. This should ideally be several folders deep, to display
to maximum effect this problem. Load the file by clicking on it
3) now click the back button to return to the directory list. You'll notice its
assumed the "closed" state it had when you first loaded it, not expanded out as
you had when you selected the file to load.

This state should persist.
Assignee: don → radha
Target Milestone: M13
Radha, is this a session history issue?
This is not Session History. The directory listing is a RDF tree. Cc'ing
waterson.
Nope, it sure doesn't save its state. Sorry. I have no idea how to fix it short
of saving the entire content model in the session history.
Status: NEW → ASSIGNED
Shall revisit after the new webshell lands. Keeping in my plate for now.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → LATER
Target Milestone: M13 → M15
LATER is deprecated...
Status: RESOLVED → REOPENED
QA Contact: don → sairuh
Resolution: LATER → ---
Target Milestone: M15 → Future
Mass moving all Navigator bugs to the Nav team. 
Assignee: radha → vishy
Status: REOPENED → NEW
Reassigning to a real person.
Assignee: vishy → sgehani
QA Contact: sairuh → paw
Product: Core → Mozilla Application Suite
INVALID?
is folder state even indicated anymore?
Assignee: samir_bugzilla → jag
QA Contact: pawyskoczka
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/20080509 SeaMonkey/2.0a1pre
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9

I can't reproduce this bug.

I close this for now as INVALID.
Reporter, if you still run into this problem while using an recent Build,
please reopen and submit actual information.
Status: NEW → RESOLVED
Closed: 25 years ago16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.