Mozilla doesn't handle nested folders it loses track of current folder.

VERIFIED WORKSFORME

Status

--
major
VERIFIED WORKSFORME
17 years ago
2 years ago

People

(Reporter: jimhurley, Assigned: law)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
I begin my application by opening a document in a folder. This document has 
links to two documents in a subfolder. The first page in the subfolder has a 
link to another sub folder below it, which should open an image in another 
subfolder, but it doesn't find it. 
'FFNW (folder)'
    beginning page (links to second page, links to third page)
    'PAGES' (folder)
        second page (references image 1, links to other pages)
        third page (links back to beginning page, same function as back button)
        other pages
        'IMAGES' (folder).
            image 1
            image 2

First link from FFNW to document in 'PAGES' doesn't open image. Then link in 
document in 'PAGES" that was linked to from 'FFNW' doesn't link to another 
document in 'PAGES'. Also when linking to a document in 'PAGES' from 'FFNW' 
that document can't be linked back to from the document in 'PAGES'. All 
documents in 'PAGES' can access each other as long as one starts in 'PAGES'. 
This is an application that will run on the user's PC from either a folder on a 
hard disk or from a CD.

I haven't tried this on Linux yet, but I will. Paths that are displayed are not 
correct, they indicate that Mozilla doesn't manage the current folder location 
correctly.

The behavior I'm trying to achieve works in IE-6, Opera 6.03, and Amaya 6.1 on 
Windows 2000 SP2 as I have the application coded.

Comment 1

16 years ago
impossible to figure out
you will have to post a test case or a url
else im pretty sure your using invalid uris
Summary: Mozilla doesn't handle nested folders it loses track of current folder. → Mozilla doesn't handle nested folders it loses track of current folder.
QA Contact: sairuh → petersen

Comment 2

16 years ago
i have a site which has a similar structure, and it works fine.

reporter (Jim): can you reproduce this bug with a recent build of mozilla (for
example, 1.2.1)? if so, please provide a testcase that demonstrates the bug. if
it's no longer a problem, please resolve this bug as WORKSFORME. thanks.

Comment 3

16 years ago
no response from reporter for >30 days, resolving invalid.

reporter: if you can reproduce this bug with a recent build of mozilla, please
reopen this bug and give details. thanks.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
(Reporter)

Comment 4

16 years ago
No longer seems to have the problem.
Status: RESOLVED → CLOSED

Comment 5

16 years ago
thanks for the followup Jim.

however, we don't use the "CLOSED" status on bugzilla, so I'll switch it to
"VERIFIED"...

reopening...
Status: CLOSED → UNCONFIRMED
Resolution: INVALID → ---

Comment 6

16 years ago
re-resolving WFM
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago16 years ago
Resolution: --- → WORKSFORME

Comment 7

16 years ago
and verified...
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.