Closed Bug 242230 Opened 20 years ago Closed 20 years ago

Ghost flashes of iframe during pageload (blinking/jumping iframe)

Categories

(SeaMonkey :: General, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 132337

People

(Reporter: stig, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7b) Gecko/20040421
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7b) Gecko/20040421

Try to load http://politiken.dk/ and notice how (at least for me) the
"Eniro" box at top-right of the page has "ghost flashes" at top-left during load
of the page. The Eniro-box is an iframe.

I see this problem on both my Mozilla installations:
1) Mozilla 1.6 on Windows XP
2) Mozilla 1.7RC1 on Windows 98

Further down on politiken.dk there's a similar problem with another iframe
(The add-banner just above the Wulffmorgenthaler comic).

Also I noticed (at least on my Moz1.6/XP) there is the same short "ghost-flash"
when tabbing to a page where politiken.dk is loaded.

I know from a comment in bug 236598
(http://bugzilla.mozilla.org/show_bug.cgi?id=236598#c14) that the jumping iframe
can be seen on some Linux systems too (same versionnumbers as my browsers).

Reproducible: Always
Steps to Reproduce:
1. Load http://politiken.dk/
2.
3.
Same behavior for another site was reported in Bug 209531
related/dup: bug 242109
Seems to be a dupe of 
Bug 228059 Flickering when floating two divs, one with overflow: auto and the
other with a:hover and display:none on imgs

See also Bug 241717  Iframe (?) makes content flash on upper screen when loading

Both bugs have testcases
dupe

*** This bug has been marked as a duplicate of 132337 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Sure this is a duplicate of bug 132337 ? Bug 132337 seems to be an old bug (from
2002), but I havn't noticed this problem until sometime this year I think, and
politiken.dk is not the only place I'm seeing it.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.