OK. Thanks. And thanks for the quick response! I appreciate how responsive this mailing list has been.
On Fri, Dec 12, 2008 at 11:23 AM, Igor Vaynberg <[email protected]>wrote: > dont use wicket:link, use bookmarkablepagelink component instead. > > -igor > > On Fri, Dec 12, 2008 at 10:19 AM, Trent Larson <[email protected]> > wrote: > > I have the following plain HTML where I want an image to be a link to > > another Wicket-managed page: > > > > <wicket:link><a href="ProductPage.html"><img > > src="../images/products_welcome.jpg" border="0"></a></wicket:link> > > > > > > The link for that page is generated fine, but then Wicket adds an > 'onclick' > > event to the 'img' tag that takes the user directly to the image: > > > > <wicket:link><a > > href="?wicket:bookmarkablePage=:com.max.web.page.ProductPage"><img > > src="../images/products_welcome.jpg" border="0" > > onclick="window.location.href='../images/products_welcome.jpg';return > > false;"></a></wicket:link> > > > > This seems absolutely wrong. The result is that a click on the image > will > > take users to directly to that image; sometimes it will then continue on > to > > the right (ProductPage) page, so users see the image by itself before > going > > to the right page, but often it just stops at the image. > > > > There is no Java code associated with this. I get it in 1.4-rc1 (as well > as > > 1.4-m3). > > > > What is happening, and how can I stop it from generating the 'onclick' > > javascript? Thanks! > > > > Trent > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
