User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:22.214.171.124) Gecko/2008092417 Firefox/3.0.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:126.96.36.199) Gecko/2008092417 Firefox/3.0.3 In my page, there is a flash content which has been tested succesfully in every browser (IE, Opera, Netscape) including previous versions of FF. After the update to 3.0.3, the content is being displayed, however, the no further interaxtion is accepted (the menu doesn´t work, neither the "Sound Off" feature. In addition, when I interact with the Flash content, the CPU Usage raises to 100% for a while. Can any of you check that the same is happening with FF 3.0.3 in your computer? Reproducible: Always Steps to Reproduce: 1.Visit http://www.simplenia.com/flash.html and try to use the menu. 2. 3. Actual Results: The Flash content is not working properly as in any other browser. The CPU Usage increases up to 100% for a couple of seconds.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/2008092417 Firefox/3.0.3 Do you mean News Company Services etc.? Appears to work normally here although you need to be patient on a 512 MB RAM laptop. Also Sound Off works fine here. Please retest in safe-mode to exclude extension problems: http://kb.mozillazine.org/Safe_Mode_(Firefox) Also, do you have the latest flash plugin?
wfm with Seamonkey trunk and Flash10RC
This is a mass search for bugs which are in the Firefox General component, are UNCO, have not been changed for 500 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.