282042 - Clicking on a link to a .wav file opens up the file, but Quicktime only plays part of the file.

Status: RESOLVED EXPIRED

(Firefox :: File Handling, defect)

Description

[GLenn Riccobono]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/0.9.3 StumbleUpon/1.993
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/0.9.3 StumbleUpon/1.993

I am in Firefox 1.0, and am checking my telephone voice mail through Optimum
Voice.  I click on a link to access my account, and then when the new mail
indicator appears, for example right now it says I have a 24 second voice mail.
 When I click on the link to listen to the voicemail, a separate Firefox window
pops up, and the message begins to play with Quicktime.  Unfortunately, the
entire message does not play.  I only hear the first 7-9 seconds and then the
message cuts off.  If I open the same link in IE, another window pops up, and
using Quicktime in the same fashion, the entire .wav file plays properly.

Reproducible: Always

Steps to Reproduce:
1. I click on my FF toolbar link to http://www.optonline.net/Home
2. I login to my account with username and password.
3. I am taken to a secure site: 
https://customer.cablevision.com/ov/VMRetrieveM.jsp?
4. The site indicates I have a new voicemail, and the length (in seconds) of the
message.
5. When I click on the link to listen to the message, a new browser window
appears, and Quicktime plays only part of the message.

Actual Results:  
I heard the first few seconds of my voicemail message, and then it stops abruptly.

Expected Results:  
Apparently the tie-in to Quicktime is affected.  When I performed the same steps
in IE, the entire .wav file is downloaded and played through Quicktime without
any problems.  It would be great if Firefox performed the same way.
Thanks for your help.

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.