The size is a layout thing. If the browser doesn't know the image
dimensions ahead of time (before downloading it) then it cannot reserve
space for it in the layout. When the image is actually downloaded, the
layout will "jump" noticably.
You should be able to reproduce this on slower dial-up connections.
Gili
[EMAIL PROTECTED] wrote:
I think jcompagner is right on this one: if the size is known, just add it to
the markup:
<img width="32" height="32" wicket:id="image"/>
Sven
But i think height and width are designer things. Because the designer >wants a
image on the place x with size y
On 9/22/05, jan_bar <[EMAIL PROTECTED]> wrote:Hi,
I think that Image should support size out of the box. Size of most >images is
known and specifying size improves rendereing in browser.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
http://www.desktopbeautifier.com/
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
