User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:184.108.40.206) Gecko/20060508 Firefox/220.127.116.11 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:18.104.22.168) Gecko/20060508 Firefox/22.214.171.124 Firefox 126.96.36.199 does not open a secondary real time video window within the http://www.infotecbsi.com/wildlife/ window. This secondary window opens fine with Firefox 188.8.131.52. Others in the relevant forum have described this same problem with the Firefox 184.108.40.206 upgrade, causing me to delay upgrading. Apparently I didn't delay long enough for your fix. Reproducible: Always Steps to Reproduce: 1.click on Bookmarks|http://www.infotecbsi.com/wildlife/ 2.After the home page opens, a real time video window should, but doesn't, appear in the center of the home page. 3. Actual Results: The real time video window doesn't appear in the center of the home page. Expected Results: A real time video window should appear in the center of the home page. This bug in the FF 220.127.116.11 upgrade has been described by others in an online forum located at http://forum.infotecbsi.com/viewtopic.php?t=7457&start=12500
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060731 BonEcho/2.0b1 I see the video (or at least a black rectangle for it fails to load here) on Firefox trunk and on Seamonkey trunk and branch but not on Firefox 18.104.22.168 and BonEcho. On BonEcho this is a regression between 1.8.1a3_2006070504 and 1.8.1a3_2006070603: http://tinderbox.mozilla.org/bonsai/cvsquery.cgi?treeid=default&module=AviarySuiteBranchTinderbox&branch=MOZILLA_1_8_BRANCH&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2006-07-05+03%3A00%3A00&maxdate=2006-07-06+04%3A00%3A00&cvsroot=%2Fcvsroot Caused by Bug 343180?
> Caused by Bug 343180? Can't be. The Java Embedding Plugin is only bundled with Mozilla.org browsers for Mac OS X.
Then maybe caused by Bug 181860?
Sounds like a duplicate of bug 346167.
Yes, it is fixed yesterday and it works now in the today's branch build. *** This bug has been marked as a duplicate of 346167 ***