309634 - Will not play audio file. The plugin finder never installs the plugins and doesnt even redirect me to a site to do it manuely.

Status: RESOLVED WORKSFORME

(Toolkit Graveyard :: Plugin Finder Service, defect)

Description

[Geoff]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

This site along w/ other ytmnd.com sites work just fine in Internet Explorer.
However, in my current version of Firefox (v.1.0.7) they do not play the sound
files. I have apple's latest version of Quicktime (7 i think) installed and it
still doesn't work. The "install missing plugins" wizard never installs the
plugins it needs.

Reproducible: Always

Steps to Reproduce:
1.Open Firefox
2.Go to http://emosong.ytmnd.com/
3.Notice how no sound plays. Open it in IE and notice how the sound does play.

Actual Results:  
I have already stated this.

Expected Results:  
Sound file plays.

Comment 1

[Jesse Ruderman]

I didn't have any plugins registered for audio/mpeg (as shown in about:plugins) on WinXP, so I had the same problem.  Once I went to Control Panel > QuickTime > Browser > MIME Settings, checked "MP3 audio", and restarted Firefox, http://emosong.ytmnd.com/ worked correctly on WinXP.

Do those directions fix it for you too?


I see three problems:

1. ytmnd has broken user-agent sniffing, causing it to send <object> (without pluginurl) to Windows Firefox users and <embed> to Mac Firefox users.

2. When Firefox encounters an <object> that it doesn't know what to do with (and that does not have a pluginurl), it doesn't show a warning like it does for <embed>.  (See bug 305564 comment 9.)

3. QuickTime for Windows doesn't register itself as being able to handle audio/mpeg in the browser by default.  (I'm not sure about this; I might have tweaked it incorrectly).

There should be separate bug reports for each of those, especially #2.

Comment 2

[Steve England [:stevee]]

Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!