Closed Bug 523931 Opened 15 years ago Closed 14 years ago

RELATIVE_ROOT of "foldername" fails while "./foldername" works

Categories

(Testing Graveyard :: Mozmill, defect)

Product:
Testing Graveyard
Component:
Mozmill
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
VERIFIED WONTFIX

People

(Reporter: merike, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; et; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)
Build Identifier: 

I would expect both "foldername" and "./foldername" work since they are really essentially the same path. Not referencing ./ results in test running with no action performed and

"Viga: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsILocalFile.directoryEntries]"  nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)"  location: "JS frame :: file:///C:/Users/Merike/AppData/Roaming/Thunderbird/Profiles/43pg1sa3.Mozmill%20new/extensions/mozmill@mozilla.com/resource/stdlib/os.js :: listDirectory :: line 42"  data: no]"

is thrown in error console.

Reproducible: Always
Depends on: 588682
I don't think we want to spend more time on fixing this old module system even with the plans of have common js available for an upcoming 1.5.1 release.

Marking as wontfix?
Whiteboard: wontfix?
Yeah, WONTFIX pending on the 1.5.1 implementation of commonJS sharedmodules..
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
Whiteboard: wontfix?
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.