Closed Bug 220435 Opened 21 years ago Closed 19 years ago

I cannot view or open Windows Media streaming videos in Mozilla, be it in the same window or in a seprate javascript pop-up window

Categories

(Core Graveyard :: Plug-ins, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: ld577, Assigned: peterlubczynski-bugs)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624

When Mozilla tries to open a Windows Media Video, one of two things happens:

1. If it is just a regular link that ends in a .wmv file, it opens it up in the
same window, but merely as a text-type page filled with a lot of gibberish
characters like this "^ˆ7#Å®XHcÆ)añJ%ÈfM¡m" (that's just a small examples, in
reality it's a whole page of that).

2. If it is a link designed to open up in a separate javascript window (i.e. a
javascript link that's something like this "javascript:NewMediaWin" and then the
name or number of the Windows Media file), it actually DOES open up in a new
javascript window, and doesn't give em gibberish. However, it then proceeds to
keep dispalying the Windows Media Player symbol and doing nothing else, even
when the clip is done loading (I have checked it with both long and short
clips...same results). It used to say that a plugin was required, but I
downloaded Windows Media Player 9 as the required plugin, and now I have the
abovementioned problem; DESPITE the fact that in the "about:plugins" section of
Mozilla, it shows Mozilla as having every MIME type plugin for Windows Media
files (asf, asx, wma, wmv, wax, wm, wvx) and shows that they are all enabled.

Reproducible: Always

Steps to Reproduce:
1.Attempt to play a streaming WMV or any other Windows Media file by clicking on it
2.Watch as one of the abovementioned two things happens.
3.

Actual Results:  
It either gave me a page full of gibberish characters, or opened it in a
javascript windows (if it was a Windows Media file that streamed and played in a
javascript window), then only showed the Windows Media symbol (the four litlle
windows boxes with the word "Windows Media" in front of it) and did nothing else.

Expected Results:  
Played the streaming WMV file
Problem 1 is a server problem, not a Mozilla problem.  The server is saying that
the file is a text/plain mime type, so Mozilla treats it as a text file and
tries to display it on screen.  The fix is for the server administrators to
correct the server setting.
Problem #2:
perhaps you want to try http://plugindoc.mozdev.org/windows.html#ActiveX
http://www.iol.ie/~locka/mozilla/mozilla.htm
Read about it at the links, and the decide to install, or not.
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.