Closed Bug 312992 Opened 20 years ago Closed 20 years ago

random flashing of ad graphics in various locations around page upon initial loading of page

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 132337

People

(Reporter: chris, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Whenever I log into the aforementioned web page (it's my homepage), the advertisement graphics imbedded in the page flash in various places around the page for about 10 seconds while the page is loading. It happens whether the add is a static image or animated flashplayer piece, or even if the add is being blocked by the Mozilla FlashBlocker (which, by the way, is an ingenious bit of programming - one of the BIGGEST reasons that I use Mozilla in the first place). Reproducible: Always Steps to Reproduce: 1. Start up the Mozilla web browser. 2. Go to www.msnbc.com 3. Watch. Actual Results: See 'Details' above. Expected Results: No flashing.
Summary: random flashing of add graphics in various locations around page upon initial loading of page → random flashing of ad graphics in various locations around page upon initial loading of page
Related to Firefox bug 301500 and Firefox bug 303178 -> Core bug 132337?
this got fixed on trunk between 20041011 and 20041012 ==> dupe of "Floating div with overflow auto flickers while resizing window or during load (reflow)" please always test with a recent build before filing (trunk, SeaMonkey 1.0 build, FF 1.5 build, etc. 1.7.x is not "recent") *** This bug has been marked as a duplicate of 132337 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
My apologies. I did do a search for similar bugs before filing, but didn't find anything since I used the keyword 'flash' instead of 'flicker'. I also mistakenly thought I had the lastest release. I have since loaded Mozilla version 1.7.12, and the problem seems to have been rectified.
You need to log in before you can comment on or make changes to this bug.