I'm pretty sure this change is a result of WICKET-1513 [1].  Please file a
JIRA that explains your behavior below.

[1] https://issues.apache.org/jira/browse/WICKET-1513

--
Jeremy Thomerson
http://www.wickettraining.com



On Mon, Apr 13, 2009 at 4:17 PM, Jeremy Thomerson <[email protected]
> wrote:

> I haven't had a chance to look back, but you could search JIRA for an issue
> that I fixed that had to do with AutoLinkResolver.  It would have been about
> in that time frame, and some things were being left our of AutoLinkResolver
> (like embed, etc).  I can't remember if I modified img tags or not.
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com
>
>
>
>
> On Mon, Apr 13, 2009 at 4:14 PM, Mike Comb <[email protected]> wrote:
>
>> Does anyone have any hints on this other than digging into the source?  I
>> found a couple of references to the same sort of request in the email
>> archives but no answers.
>>
>>
>>
>> On Apr 9, 2009, at 5:42 PM, Mike Comb wrote:
>>
>>  Hi, I'm trying to upgrade several sites from 1.4m3 to 1.4r2 and have hit
>>> an issue with the AutoLinkResolver.  We have lots of html with linked images
>>> that look like this:
>>>
>>> <wicket:link><a href="SomePage.html"><img src="/some/full/path/image.gif"
>>> /></a></wicket:link>
>>>
>>> This used to work fine, but with the last couple of releases (r1 and r2)
>>> clicking on the image directs the user to a blank page with the image on it
>>> rather than the intended page link through a javascript onclick action.
>>>  Ideally I'd like to turn off processing of img tags by the AutoLinkResolver
>>> and only have it process href's, but I can't figure out how to do that from
>>> the javadocs.  Can someone point me in the right direction?  Going back and
>>> setting each of these up as a BookmarkablePageLink is not an option, we need
>>> the auto linking behavior.
>>>
>>> Thanks,
>>> -Mike
>>>
>>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>

Reply via email to