You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2010/09/24 20:40:34 UTC

[jira] Resolved: (WICKET-1936) Client-Side Image Map

     [ https://issues.apache.org/jira/browse/WICKET-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-1936.
-------------------------------------

    Fix Version/s: 1.4.13
                   1.5-M3
                       (was: 1.5-M2.1)
       Resolution: Fixed

The patch is applied and the new ImageMap implementation is ported to 1.4.x so the users can migrate to the new one before upgrade to 1.5.x

> Client-Side Image Map
> ---------------------
>
>                 Key: WICKET-1936
>                 URL: https://issues.apache.org/jira/browse/WICKET-1936
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.3.5, 1.4-RC1
>            Reporter: James Carman
>            Assignee: Martin Grigorov
>             Fix For: 1.4.13, 1.5-M3
>
>         Attachments: ClientSideImageMape.patch, WICKET-1936.patch
>
>
> The existing ImageMap implementation does not allow you to "attach" it to any Image component.  Also, it only works with Link objects (and thus not AjaxLinks or ExternalLinks).  The new client-side image map implementation attaches itself to any existing image and supports any AbstractLink object.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.