Closed Bug 6194 Opened 25 years ago Closed 25 years ago

nsFileSpec shouldn't accept UNIX path

Categories

(Core :: XPCOM, defect, P2)

Product:
Core
Component:
XPCOM
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: bugzilla, Assigned: mcmullen)

Details

in order to be compatible with Mac behavior and avoid future platform parity problem, nsFileSpec should not accept to be created or set from a UNIX path but from a native path. nsFileSpec should generate an assert error when a UNIX path is used like on Mac.
Priority: P3 → P2
Target Milestone: M6
John, is this a bug?
If I may paraphrase: On Macintosh, the code asserts if a unix path is passed in to nsFileSpec. On Windows, it does not - the code goes ahead and works. Making it assert on Windows would stop people developing on windows from writing code that works on Windows and not on the Macintosh. So it's not a bug, but it is a feature request that may prevent MANY future bugs.
Status: NEW → ASSIGNED
Accepting bug
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I put in an assert, and checked this in. Marking fixed.
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.