288903 - mailcap nametemplate is respected in download manager, but not with helper app

Status: RESOLVED EXPIRED

(Firefox :: File Handling, defect)

Description

[Knut Forkalsrud]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0

The URL above may require registration to exhibit the problem.  The deal is that
the response content type is audio/x-mpegurl
In my /etc/mailcap I try to have it saved with an ".m3u" extension so that xmms
can interpret it as an mp3 url:

audio/x-mpegurl; xmms %s; nametemplate=%s.m3u

The nametemplate is not respected.  I can see the file in /tmp with the name
"m3u.html" as would be a reasonable default guess from Firefox based on the URL.
It would be nice if .m3u was appended to the filename.

The interesting aspect is that if I right click on the link and select "save
target As..." the nametemplate is respected and the dialog box correctly
suggests m3u.html.m3u as file name.  However if I left click on the link and get
the dialog box that asks me whether I want to open it using some application or
save to disk, and then go for the save option, the suggested filename does not
have the nametemplateapplied.

Reproducible: Always

Steps to Reproduce:
See details section
Actual Results:  
the file gets saved with the wrong extension and xmms cannot interpret is as an
m3u file.

Expected Results:  
The nametemplate in /etc/mailcap should be consistently respected for all
downloads, including for helper applications.  Not just in the download manager.

Comment 1

[Gervase Markham [:gerv]]

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/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.