Martijn Dashorst wrote: > I guess this should go into Wicket NG (2.0/1.5) as a > replacement for the current image map. I don't think it is a > problem that we break backwards compatibility for a couple > components in the release after the generics release. ... > I'll add this one to the wish list and assign the correct > Wicket version for this patch. We'll get back to this one > when we start 1.5/2.0. Thanks!
I don't think it's actually necessary to break backwards compatibility. The ImageMap could provide the old behaviour if it's linked to an <img> tag, and the new behaviour if it's linked to a <map> tag. I think that's a pretty easy check, and it could mean this fix can be included in 1.4. Unless 1.4 is in too much of a hurry to wait for a newbie's patches. I can understand that. mcv.
