Closed Bug 189273 Opened 22 years ago Closed 20 years ago

cannot view video stream (wvx)

Categories

(Core Graveyard :: File Handling, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tom, Assigned: law)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130

Click on any of the video stream links.  

Windows Media Player (9 Series) does come up but error out with "The selected
file has an extension that is not recognized by the Windows Media Player, but
the player still be able to play it.  Because the extension is unknown by the
Player, you should be sure that the file comes from a trustworthy source".  When
I click Yes, if gives me a fatal error "Windows Media Player encountered an
unknwon error".

The same link works on IE.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Actual Results:  
Windows Media Player (9 Series) does come up but error out with "The selected
file has an extension that is not recognized by the Windows Media Player, but
the player still be able to play it.  Because the extension is unknown by the
Player, you should be sure that the file comes from a trustworthy source".  When
I click Yes, if gives me a fatal error "Windows Media Player encountered an
unknwon error".

The same link works on IE.


The "recently opened files" list shows scrambled (msdos 8-char) filenames. 
Maybe Mozilla downloaded the file, renamed it, and that's why it's not working.
wfm with a one day old win2k build and the mediaplayer 6.4 + Mediaplayer-Plugin
->File Handling
Assignee: asa → law
Component: Browser-General → File Handling
QA Contact: asa → petersen
Reporter: Is this still a problem with a current Mozilla build?
WFM with Mozilla trunk build 2004103006 on Windows XP SP2.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.