We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

My homepage has the following code: <body onload="playSound('ding 2.wav')">.

  • 1 reply
  • 9 have this problem
  • 27 views
  • Last reply by cor-el

more options

I have this code on my homepage: <body onload="playSound('ding 2.wav')">. It has worked on and off during all of the Firefox 4 betas, and now in the release, it doesn't work again. Is there some way I can get it to work consistently. It works consistently in 'Chrome' and 'IE9', but intermittently in Firefox. It seems that every time it got fixed in the beta, the next release would break it again.

I have this code on my homepage: <body onload="playSound('ding 2.wav')">. It has worked on and off during all of the Firefox 4 betas, and now in the release, it doesn't work again. Is there some way I can get it to work consistently. It works consistently in 'Chrome' and 'IE9', but intermittently in Firefox. It seems that every time it got fixed in the beta, the next release would break it again.

All Replies (2)

more options

Can you post a link?
Do you specify a MIME type to make Firefox use a specific plugin?

  • WMP: type="application/x-mplayer2"

A good place to ask questions and advice about web development is at the mozillaZine Web Development/Standards Evangelism forum.
The helpers at that forum are more knowledgeable about web development issues.
You need to register at the mozillaZine forum site in order to post at that forum.

See http://forums.mozillazine.org/viewforum.php?f=25

more options

No URL. The homepage is just a local homepage.

Yes, I have it set to play .wav files with the quicktime plugin. As I said before, it would work in the every other beta release. Just when I thought they had it resolved, the next release comes out and breaks it again.