171369 - images distorted on first pageload

Status: RESOLVED FIXED

(Core :: Layout: Images, Video, and HTML Frames, defect)

Description

[Wessel de Vries]

When I load a page for the first time, images are distorted (too big).
This also applies to buttons generated with the <input type=button> tag.
Also too big.
I must point out that every element in my page is in a <span> tag, and this is
shown or hidden by style="display:...". There are also lots of tables implemented.
The buttons or images themself do not have any style or width/height parameters.
When I reload the page everything returns to normal.

This effect happens every time I load the page for the first time.
If I reload it, it displays oke, but if I move to another page and back again
all images and buttons are too big again.

By the way: finally a speedy and reliable browser for the Macintosh platform!

Comment 1

[Mats Palmgren (inactive)]

Please provide an URL where you see this problem.
What version of Mozilla are you using?

Comment 2

[Wessel de Vries]

Attachment: html page+images

attached you'll find a zip with a html page and images, stylesheet and
javascript include file.
copy this to your webserver and try this:

1. mozilla cache options: every visit to page, then clear mem cache and clear
disk cache
2. open testmenu.htm; images are distorted (this would also happen with html
buttons)
3. reload page; images are OK
4. execute step 1 and 2 again; images distorted again.

Strange thing: delete or rename the javascript file (formsupport.inc), and the
effect does not appear....

I've tested this on mozilla 1.1 and 1.2a, on Apple and PC systems.
You can also check it out on our webserver:
http://212.142.7.108/test/testmenu.htm

Wessel de Vries

Comment 3

[Mats Palmgren (inactive)]

Confirming bug, 2002-10-01-08 trunk Linux.

Comment 4

[Mats Palmgren (inactive)]

Attachment: Screenshot of bug (images are scaled initially - Reload fixes it)

Comment 5

[Jim Dunn]

"mass" re-assigning of bugs from pav to myself

Comment 6

[Jim Dunn]

This seems to have been fixed somewhere between 1.2.1 and 1.3a.
I see the problem with 1.2.1 on win2k, but I don't see it with
1.3a/1.3b on the same machine.  Marking fixed (note: i am not sure
what was done to fix this.)