[
https://issues.apache.org/jira/browse/WICKET-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-1456.
-----------------------------------
Assignee: Igor Vaynberg
Resolution: Won't Fix
in 1.5 ImageMap is replaced by ClientSideImageMap that should cover this usecase
> ImageMap blocks Image functionality
> -----------------------------------
>
> Key: WICKET-1456
> URL: https://issues.apache.org/jira/browse/WICKET-1456
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.2
> Reporter: Martijn Vos
> Assignee: Igor Vaynberg
> Fix For: 1.5-M2
>
> Attachments: wicket-1456.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> ImageMap is applied to an img tag, which means you can't apply an Image to
> that tag anymore. Since ImageMap does not supply the functionality of Image,
> this means it's impossible to treat an imagemap's image like a Wicket image
> (including dynamic rendering). And because ImageMap is final (why?), it's
> also not possible to extend it and add that functionality.
> I see three possible fixes:
> 1: The easiest and ugliest fix: make ImageMap not final, and have the user
> figure it out.
> 2: Add Image functionality to ImageMap. This duplicates functionality (since
> ImageMap can't inherit directly from Image), and might give problems in the
> future when new functionality is added to Image.
> 3: Consider the current ImageMap broken, and replace it with a different
> approach: apply ImageMap to a <map> tag, use a regular image for the <img>
> part, and add to Image a method to link it to an ImageMap. I prefer the third
> solution, although it will break compatibility with existing ImageMaps.
> Perhaps a new DynamicImageMap could be added?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
