Closed Bug 273707 Opened 20 years ago Closed 17 years ago

Download manager ignores preferred application

Categories

(Toolkit :: Downloads API, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 236389

People

(Reporter: resuna, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 StumbleUpon/1.999
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 StumbleUpon/1.999

I have selected a third-party application (Mount) to handle DMG images. When
Firefox downloads a DMG image it sometimes sets the file type and owner to some
random gibberish (eg: ' !î`') and opens them in Disk Copy.

Reproducible: Sometimes
Steps to Reproduce:
1.Download http://www.indyjt.com/software/iEatBrainz/iEatBrainz_source.dmg
2.Select "Open" from download manager, or
3.View finder info.

Actual Results:  
Opened in Disk Copy, file 'owner' was ' !î`'.

Expected Results:  
Opened in Mount, file owner should be <None>.
This only applies to DMG files.

*** This bug has been marked as a duplicate of 253004 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
This is not a duplicate of 253004 - this has nothing to do with Firefox
preferences, or whether Firefox uses LaunchServices for DMG files, it's about
Apple's preferences as set in Finder. Whatever the user's set in the Firefox
preferences, it should save the files with either the correct Finder info or
with NO Finder info... it's never appropriate to put random data in the Finder info.

This is not necessarily just DMG files, I've occasionally found other files I've
downloaded with odd Finder Info, but I haven't been able to reproduce the
problem as reliably.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
When I download a .dmg file its creator get set to "hDmp" (HexEdit) and type
"BINA". It seems consistently repeatable.

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
(In reply to comment #3)
> When I download a .dmg file its creator get set to "hDmp" (HexEdit) and type
> "BINA". It seems consistently repeatable.

Note that this is also not appropriate.

Firefox MUST save files using either the LaunchServices settings, or with no
Finder type/creator flags. It MUST NOT generate the Finder type/creator
information if it's not capable of setting it correctly.
Verified: it is no longer setting the type/creator to random gibberish, but it's
still setting it to hDmp/BINA.
Assignee: bugs → nobody
QA Contact: aebrahim-bmo-507 → download.manager
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4

This behaviour (incorrect/inappropriate type and creator set for downloaded dmg [and PDF files]) has been a long-standing irritation for me with Mozilla and now SeaMonkey. I believe that it's part of the problem described in Bug 236389.

Peter: Perhaps this bug should be marked a duplicate of Bug 236389? (please do so, if you agree)
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago17 years ago
Resolution: --- → DUPLICATE
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.