Closed Bug 72913 Opened 24 years ago Closed 24 years ago

[RFE]need File.isWritable()

Categories

(Core Graveyard :: Installer: XPInstall Engine, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: dbragg, Assigned: slogan)

Details

Attachments

(4 files)

XPInstall needs to expose a File.isWritable() so script authors doing direct i/o type stuff can keep themselves out of trouble.
Keywords: nsbeta1
Keywords: nsbeta1nsbeta1+
Keywords: nsbeta1+nsbeta1-
Fix a bug, get a clue.
Assignee: dveditz → syd
Dan, samir -- looking for r= and sr= on this.
Status: NEW → ASSIGNED
Drop the fileIsWritable name (the file*() names are deprecated in favor of File.*()). Else looks good. Contingent upon dropping this name r=sgehani.
samir, if you look at the test JS I wrote, I am using isWritable. I just copied the existing patter, internally looks like fileIsWritable, fileIsDirectory and such are used. We should make any deprecation you refer to in one fell swoop, not just for my code, so as to maintain consistency. When are you planning to do this change, if ever?
sr=dveditz with comment change discussed via IM. I don't care about the redundant fileIsWritable, we can nuke that later.
Fixed
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Build: 2001-05-17-07-trunk(WIN), 2001-05-17-08-trunk(MAC), 2001-05-17-08-trunk(LINUX) Looks good on all platforms. http://jimbob/jars/a_fileop_iswritable.xpi Marking Verified!
Status: RESOLVED → VERIFIED
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: normal → enhancement
For me this one seems to fail with Mozilla 1.7.11! An "isWritable" on an existing file always returns "true" and an "isWritable" on an non existing file always returns "false". Could someone please reopen this one?
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: