Closed
Bug 530188
Opened 15 years ago
Closed 14 years ago
Recursing of directory entries somewhere inside a symlink returns files in the target of the link
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
blocking2.0 | --- | betaN+ |
People
(Reporter: mossop, Assigned: jaas)
References
Details
This appears to be an OSX problem only and doesn't happen on Linux. If I do the following: var file = Components.classes["@mozilla.org/file/local;1"].createInstance(Components.interfaces.nsILocalFile); file.initWithPath("/var/folders"); var de = file.directoryEntries.QueryInterface(Components.interfaces.nsIDirectoryEnumerator); var newfile = de.nextFile; where /var is a symlink to /private/var then after running newfile's path is "/private/var/folders/foo" as opposed to "/var/folders/foo" as I'd expect (and as seen on Linux). This causes all sorts of oddities like newfile.parent != file, etc.
I think this needs to block 2.0, we shouldn't have changed this behavior. This is fixed by the patch on bug 571193.
blocking2.0: --- → betaN+
Fixed by the patch on bug 571193.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•