nsFileSpec += operand does not work correctly on Mac

RESOLVED FIXED in M6

Status

()

Core
XPCOM
P1
normal
RESOLVED FIXED
19 years ago
19 years ago

People

(Reporter: dougt, Assigned: mcmullen)

Tracking

Trunk
PowerPC
Mac System 8.5
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
Appending to a nsFileSpec via the += operand does not work for more than a
filename.  Here is a code snippet:

// initalPath is some real directory

nsFileSpec fileSpec(initalPath);
fileSpec += "nested/file.txt";

At this point fileSpec does NOT equal the expected initialPath plus "nested/
file.txt".  In the diff that I send you John, I have included a testcase that
will reproduce this problem.

This problem does not exist for windows, and pretty sure it does not for Unix.

Updated

19 years ago
Priority: P3 → P2
Target Milestone: M5

Comment 1

19 years ago
Set milestone to M5.

John, should you fix this for M5?
(Assignee)

Comment 2

19 years ago
This is blocking dougt a little, but I am not sure whether he requires it before
M5. I was planning to fix it for M5, but is it required? Doug?
(Reporter)

Comment 3

19 years ago
This is not *required* for m5.

Updated

19 years ago
Target Milestone: M5 → M6

Comment 4

19 years ago
Doug Turner says he doesn't need this until M6.
(Assignee)

Comment 5

19 years ago
Accepting
(Assignee)

Comment 6

19 years ago
Changing to P1 the priority of bugs upon whose solution others are waiting.
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
QA Contact: 4250 → 4737
Resolution: --- → FIXED
(Assignee)

Comment 7

19 years ago
FIx checked in. Assigning dougt as qa contact.

Comment 8

19 years ago
Bulk moving to XPCOM, in preparation for removal of XP File Handling component. 
(XPFH has received two bugs in ~5 months, and is no longer in active use.)
Component: XP File Handling → XPCOM
You need to log in before you can comment on or make changes to this bug.