Closed
Bug 301914
Opened 19 years ago
Closed 19 years ago
flash objects randomly moving on the screen on page load
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: petr, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.10) Gecko/20050723 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.10) Gecko/20050723 When visiting http://zpravy.idnes.cz/, during the page load the flash advertisement is randomly appearing on several places on the screen, is flickering. It is the same behavior as described in bug 291578, but bug 291578 is for Firexox on Linux, and I use Mozilla on Windows 98 and Windows XP. It seems to be platform independent. Reproducible: Always Steps to Reproduce: 1. Go to http://zpravy.idnes.cz/ Actual Results: During page load, flash objects are diplaying on random places. Expected Results: They should appear on the right place only.
Comment 1•19 years ago
|
||
wfm with a current trunk build, reopen if you still can reproduce this with a current build (like current SeaMonkey trunk).
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 2•19 years ago
|
||
I cannot verify this because current trunk builds of Mozilla Seamonkey like seamonkey-1.0a.en-US.win32.installer.exe does not work on Windows 98 - just logo appears for a fraction of second and then dies quietly. I worry to install it on my main Windows XP computer. Is there any possibility to backport the fix to 1.7.x ?
Comment 3•19 years ago
|
||
No i just looked a bit around this probably related to the Widget caching bug fix, no way this fix can be backported to Mozilla 1.7.x
| Reporter | ||
Comment 4•19 years ago
|
||
Thank you for your comment, in the meantime I was able to find bug 301043 and the workaround - installing with additional parameter: seamonkey-1.0a.en-US.win32.installer.exe -greLocal This enabled me to run the SeaMonkey - and the problem is really fixed there.
You need to log in
before you can comment on or make changes to this bug.
Description
•