Sometimes a plugin gets filled with artifacts zooming a page -- using the green button in the browser window's upper-left to "maximize" or "restore" it. But (oddly) sometimes the same plugin in another page doesn't have this problem. This happens only on OS X (I've tested on 10.6.4 and 10.5.8). Here's a page that demonstrates the problem ("page A"): http://cat-lovers-blog.com/3273/nora-practice-makes-purr-fect-check-the-sequel-too-2/ Here's another page ("page B"), containing the same YouTube video, which doesn't demonstrate it: http://www.youtube.com/watch?v=TZ860P4iTaM Steps to reproduce: 1) Start a Minefield nightly and visit one or the other of the previously mentioned URLs. 2) Click the green button in the left part of the title bar to maximize the page. Then click it again to restore the page to its previous size. With the "Page A" you'll find that the video of the piano-playing cat is now filled with bits and pieces from elsewhere in the page. With "Page B" you shouldn't see any problems. Presumably there's some difference between the two pages that explains this. I don't (yet) know what that is.

This bug is quite old. The regression range is firefox-2010-01-11-03-mozilla-central firefox-2010-01-12-03-mozilla-central http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2010-01-11+03%3A00%3A00&enddate=2010-01-12+03%3A00%3A00 In this range I suspect the patch for bug 526394.

Roc, do you have any idea why "Page A" demonstrates the bug but "Page B" doesn't?

I should be able to get to this eventually -- maybe during the upcoming work week.

This should probably at least block the final release.

Are you seeing bug 561126?

> Are you seeing bug 561126? No. This bug's regression range is different.

Steven - are you still seeing this? I can't repro.

No, I can't reproduce this anymore. It was fixed in the 2010-09-19-03-mozilla-central nightly: http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2010-09-18+03%3A00%3A00&enddate=2010-09-19+03%3A00%3A00 I suspect one of Mats Palmgren's patches for bug 449734 fixed this, or possibly his patch for bug 596022.