Closed Bug 596951 Opened 15 years ago Closed 15 years ago

Relative path support for webapp and profile

Categories

(Mozilla Labs :: Prism, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: matthew.gertner, Assigned: matthew.gertner)

Details

Attachments

(1 file, 1 obsolete file)

In some cases (e.g. placing an app on removable media) it is necessary to specify relative paths for the webapp configuration files and profile. Currently Prism supports only absolute paths.
Attachment #475818 - Flags: review?(mark.finkle)
Attachment #475818 - Flags: review?(mark.finkle) → review+
I found a problem with the previous patch. On Mac, when the extension manager asks for restart, the directory is changed to the one where the executable is located in the app bundle. By coincidence, this is at the same level in the bundle as the directory containing application.ini, which is where the relative paths are calculated from. As a result, the stat() call in SetEnvironmentVariable (which I was using as a kluge, assuming the path might be relative if the file can't be found) succeeds and the path isn't resolved. Execution fails later since there are places where an absolute path is assumed.
Attachment #475818 - Attachment is obsolete: true
Attachment #476812 - Flags: review?(mark.finkle)
Comment on attachment 476812 [details] [diff] [review] Fixed relative path detection on OS X nice explanation
Attachment #476812 - Flags: review?(mark.finkle) → review+
Sending client/stub/nsPrismStub.cpp Transmitting file data . Committed revision 75207.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: