289911 - No direct Playerstart when clicking on a wmv-file URL

Status: RESOLVED INVALID

(Core Graveyard :: File Handling, defect)

Description

[Ruediger Lahl]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050410
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050410

The wmv-Videoformat is known by the Helperapplication-section in the Preferences
of my Mozilla, but when I click on an URL to a wmv, Mozilla ask: 'what should
Mozilla do with this file'
Preselectet is 'Open with the default Application(BSPlayer)'.
'[_]Allways perform this action when handling files of this type' is gray and
can't switched on :-(

An older build(20050222) works fine for me.

Reproducible: Always

Steps to Reproduce:
1.click an URL to a wmv-file.
Actual Results:  
Mozilla ask: 'what should Mozilla do with this file'

Expected Results:  
Mozilla should start the Player who is given in the Helperapplication Sector of
the Preferences for wmv-files.

It seems, that only wmv-files are affectet. mpeg/mov/avi are working fine.

Comment 1

[Frank Wein [:mcsmurf]]

That page sends text/plain as MIME-Type, so i'm not sure if this isn't
intentional...

Comment 2

[Ruediger Lahl]

(In reply to comment #1)
> That page sends text/plain as MIME-Type, so i'm not sure if this isn't
> intentional...

The wmv is linked in this page: http://www.alohafunwear.com/multimedia.shtml

The Realplayer- and Quicktimefiles on this side calling her players directly.
The wmv-files work for me too in my older 20050222-Nightly.

Maybe the MIME-Type is not correkt, but its affect only wmv and it not affected
wmv in my older Mozilla-Nightly.

Comment 3

[Matthias Versen [:Matti]]

The realplayer and quicktime files are send with the correct mime-type.
(easy to check with http://web-sniffer.net).

The change seems to be from bug 285517 (see comment#5 there).
Biesi should decide if this is by design....

Comment 4

[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 5

[Darin Fisher]

I can confirm the reported behavior.  I'm not sure what we want to do about
text/plain documents served like this.  IE loads the WMV file directly into
Windows Media Player.

Comment 6

[Boris Zbarsky [:bzbarsky]]

If the type we sniff to is not something supported internally we should show the
helper app dialog with the user's default action preselected.  We should NOT
just launch the helper without checking with the user, since that would allow
various firewall-bypassing security exploits.  Sounds like everything is working
as designed to me... what am I missing?

Comment 7

[Darin Fisher]

bz: Yeah, I agree with you.  This is working as designed.  Marking INVALID.

You can configure the browser to send WMV automatically to Windows Media Player,
but by default it should prompt.

Comment 8

[Ruediger Lahl]

(In reply to comment #7)

> bz: Yeah, I agree with you.  This is working as designed.  Marking INVALID.

Thank you for marking. This bug can be closed.