156130 - "Show File Location" opens explorer in wrong view mode

Status: RESOLVED WONTFIX

(SeaMonkey :: Download & File Handling, defect)

Description

[Dave Warren]

The "Show In Explorer" button opens a single folder view (Without the tree) even
when the file associations in Windows normally open a full "Explorer" window. 
Mozilla should honour the default Windows setting.

Comment 1

[Dimitrios]

I think it's a valid, though minor issue. Opening Windows Explorer with folder
tree to the left is better for identifying the location of the file
(particularly with the default Windows setting that hides folder path).

Comment 2

[J.K.Umeboshi]

Since very old builds, on Windows PCs, the now called "Show File Location"
button  just opened an Explorer window showing the contents of the folder where
the dowloaded file should be located, but not selecting the file. If the folder
is already open (ie pressing the button again) it automatically select the file
in the folder.
We would expect that the file would be selected also if the folder was not
already open.
This is a really minor issue that but maybe can be resolved very quickly...

I'm writing here because I think what I'm reporting can be related to the bug
reported here.

Workaround: just press the "Show File Location" button twice to open the target
folder and select the dowloaded file.

Comment 3

[Andreas Kunz]

I don't see how this is a bug:
How do I get Windows Explorer to always open folders with the folder tree at the
left? I open it and select ~"use this folder's settings or all folders", but no
folder ever has that tree no matter how I open it.

How do you open up folders from other applications so this does work?
Maybe they start explorer with different parameters or something?

Comment 4

[Brodie]

Mozilla just calls windows explorer to open a window for the folder. So windows
itself isn't worrying about that setting. Just click the 'Folders' button in the
toolbar of the explorer window and they'll be displayed. This should be closed
as WONTFIX.

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Robert Kaiser]

The SeaMonkey team has no intentions on working on this.