Last modified: 2008-10-06 04:29:42 UTC
Please have a look at the given URL and try to click all links on
the right. The ones directly aside the image are not clickable.
This also happens when <imagemap> is included in wikitables,
or when it is accompanied by other simple <div>s with float,
align or such.
The only two browsers that allow clicking all links in this example
(correctly, as expected) seem to be Opera 9.10 (on Mac) and IE7 (on WinXP).
FireFox (1.5.x and 2.0x), Safari, Konqueror, Camino and others make
some links unclickable.
ImageMap currently fails to be useful in many cases therefore,
e.g. if you want to use imagemap near the top of the article
about [[Australia]] so that it gets displayed aside the large infobox.
Thanks in advance for fixing :-)
Table looks ok...
Testing in Firefox 2.0, the floating problem appears to be triggered by the
"position: relative" style on the enclosing <div>.
As far as I can tell, "position: relative" with no offset *should* act
identically to the default (implied "position: static"), which of course means
it shouldn't even be there... I think. :)
* with position: relative the links in the float don't work where they overlap
the <div>'s box (more easily visible if you set a border)
* without position:relative, the info link icon goes zipping around to the wrong
location, up in the previous paragraph or something.
Sounds like a bug shown by a workaround for another bug, or... something.
position: relative with no offset acts as a bound for position: absolute elements inside it, for
one. For instance, <div style="position: relative;"><div style="position: absolute; left:
1em;">Foo</div></div> will have "Foo" 1em from the left of the relative-positioned div, not the
body. That's why the info link goes somewhere else if you go to position: static.
The issue seems to be related to the fact that the containing block extends all the way to the
edge of the page; the links only fail when the box overlaps them. If we give an appropriate pixel
width (which should be easy, since we know the pixel size of the contents), the problem disappears.
Just to correct myself about what I meant with "wikitables" at #1 ...
Well, no "inclusion", obviously, but generally the same behaviour as for <div>s.
I was testing to much stuff today, so I mixed it up a bit, sorry ;-)
A fix for this bug is available in conjunction with that for bugs 8718 and 9126.
See bug 9126 for info.
Assigned to extension developer
Fixed in r41720/r41725.