Closed Bug 42054 Opened 25 years ago Closed 24 years ago

XP file picker cannot expand native paths

Categories

(Core :: XUL, defect, P3)

x86
Linux
defect

Tracking

()

RESOLVED FIXED
Future

People

(Reporter: jwbaker, Assigned: bryner)

Details

(Keywords: helpwanted)

On Linux build 2000060908 (M17), the XP file picker doesn't understand paths. Typing "/home/jwb/index.html" or "~/index.html" or "/*/jwb/index.html" are more than Mozilla's tiny brain can handle. On the console, I get these errors after I click "Ok" in the dialog: JavaScript error: line 0: uncaught exception: [Exception... "Component returned failure code: 0x80520001 [nsIFile.append]" nsresult: "0x80520001 (<unknown>)" location: "JS frame :: chrome://global/content/filepicker.js :: onOK :: line 86" data: no] The expected behavior it for Mozilla to resolve the path the same way that the Unix shell would, or the equivalent for other platforms.
assigning to bryner, nominating for nsbeta3. If we do this, it would have to be platform-specific, since paths aren't even used on all platform's file pickers (e.g., it is expressly forbidden by Mac UI guidelines)
Assignee: trudelle → bryner
Keywords: nsbeta3
setting to New
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
okay to fix if it is just a call to normalize the path, but not worth the risk of writing new code to do this.
Whiteboard: [need info]
This would require additional code. nsIFile::Normalize does not understand ~ -- it calls realpath() which only deals with ".." type expansions. Removing [need info] and nsbeta3 keyword, marking Future.
Keywords: nsbeta3
Whiteboard: [need info]
Target Milestone: --- → Future
.. but a nice patch would be most appreciated :-]
Keywords: helpwanted
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.