On Thu, 10 Mar 2005 11:29:37 -0500, Gili wrote:
>On Thu, 10 Mar 2005 08:15:51 -0800, Jonathan Locke wrote:
>
>>not really advisable. you should use a regular img tag or wait for css
>>support i think...
>
> If I could do round corners with normal <img> tags, I would,
>but to the best of my knowledge this is impossible because all the
>classic html tags are of type "display:block" which means they get ugly
>spacing around them which will cause the round corner to misalign in
>unpredictable ways across browsers. Really, I don't think I have much
>choice. If I wanted to subclass Image to change this behavior, how
>would I do it?
Actually, I just had a thought. Maybe I can insert <img> tags
with "display:hidden" in my HTML code. From Wicket's point of view,
there is a reference to an Image component (even though it is invisible
and will never get rendered) and from the browser's point of view, it
still gets the image it wants. What do you think? Seems like a much
cleaner hack to me.
Another thought is: if I place the <img> tag within a
<wicket:remove> will Wicket be smart enough to complain about the
component not getting referenced? :)
Gili
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
