Closed Bug 74606 Opened 23 years ago Closed 23 years ago

Cannot change drives when using the filepicker.xul dialog

Categories

(SeaMonkey :: UI Design, defect)

x86
OS/2
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WONTFIX
Future

People

(Reporter: jblanco, Assigned: bryner)

References

Details

(Keywords: qawanted)

Attachments

(1 file)

You cannot change drives when using the filepicker dialog 
(filepicker.xul). Cannot open a file from a different drive 
or save to a different drive than what the filepicker opens 
up with. Happens on all OSes using filepicker.xul.
bryner is rewriting this dialog, however i don't think anyone even thought 
about this problem (windows uses native file picker)
Assignee: asa → bryner
Component: Browser-General → XP Apps
OS: other → OS/2
QA Contact: doronr → sairuh
Hardware: Other → PC
would this occur on unix? on linux, eg, i don't have a problem opening or saving
to different *partitions*, at least... perhaps this is os/2-specific?
yes, well, it's basically os/2 specific (hence os/platform), however if we ever 
switch windows to xp filepicker, it'd appear there, I have no idea about mac (i 
hope we use nav services and avoid the issue).

mkaply: I don't remember the reason you guys didn't use a native filepicker, 
could you tell us?
I don't think there's time for this for 0.9.  mkaply, do you think you could
help on this one?
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.1
This one is on our radar. We would certainly like to use the XP file picker on 
OS/2 in the future.

We do have a native filepicker. Unfortunately though when we switched widget to 
use proper component registration instead of nsSetupRegistry, we started getting 
the XP filepicker instead of the native filepicker.

Relevant code is at:

http://lxr.mozilla.org/seamonkey/source/widget/src/os2/nsWidgetFactory.cpp#252

We believe it's probably a timing issue.

For 0.9, we will simply not package nsFilePicker.js so the problem won't happen, 
but does anyone have any idea how you force one component over another in 
component registration?

Or should we not be putting nsFilePicker.js in components for OS/2 until we get 
it working?
I would simply change xpfe/components/filepicker/Makefile.in to not go into the
src directory (for OS2) if you don't want the xp filepicker to be used.  Trying
to make components override each other sounds like it's asking for problems.
Silly question

Should I change filepicker/Makefile.in? Or should I just change the components 
makefile to not go into the filepicker directory at all?

Or maybe we should add a configure option for the XP filepicker?
Windows goes into filepicker/res/locale, so that it can install the properties
file... you'll probably want to do the same.
*** Bug 77577 has been marked as a duplicate of this bug. ***
Target Milestone: mozilla0.9.1 → mozilla0.9.3
r=cls
Pushing this out, we have no plans to turn on the xul filepicker on any non-unix
platforms in the 0.9.3 timeframe.
Target Milestone: mozilla0.9.3 → mozilla1.0
using the xul filepicker for non-unix systems really isn't a high priority...
Target Milestone: mozilla1.0 → Future
Brian,

Do you think this is something we will ever want for any platform besides OS/2?

If not, we can kill this bug - we rewrote our file picker on OS/2 and it works 
very well so we don't need to use the XP one anymore.
doubtful.  let's kill it.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Verify. we don't need this anymore.
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: