Mozilla Firefox 1.0.4 causes 3 seperate instances of RealPlayer to open when a streaming video link is clicked.




File Handling
13 years ago
12 years ago


(Reporter: raid517, Unassigned)


Firefox Tracking Flags

(Not tracked)





13 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Build Identifier: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Hi since updating to Firefox 1.04 whenever I visit and click on watch video (any video)
RealPlayer will launch three seperate instances of itself and begin playing 3
seperate instances of the same stream. Equally anoying is that RealPlayer used
to play embedded within Firefox - but it no longer does this. I was originally
able to resolve this by deleting everything I could find to do with realplayer
from my PC 9including the realplay plugins from my mozilla firefox directory)
and starting with a fresh profile - but it has just remerged and this fix no
longer appears to work. I only have realplayer 10 installed. I do not have
realplayer 8 installed too, nor do I have multiple instances of real player 10

Does anyone have a clue how to fix this?


Reproducible: Always

Steps to Reproduce:
1.Update Firefox from 1.03 to 1.04
2.Click on a streaming video link from the above site.

Actual Results:  
Clicking on a streaming video link will cause three seperate instances of
realplayer 10 to be launched.


Expected Results:  
Launch on instance of realplayer embeded within the web page - as it used to do
in consistantly and without error in realplayer 1.03.



13 years ago
Summary: Mozilla Firefox 1.04 causes 3 seperate instances of RealPlayer to open when a streaming video link is clicked. → Mozilla Firefox 1.0.4 causes 3 seperate instances of RealPlayer to open when a streaming video link is clicked.


13 years ago
OS: Windows XP → Linux

Comment 1

13 years ago
Note. Sorry the OS this happens on is Linux. Not windows XP.

Changed above.

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:
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.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.