Sent by Ingo Chao on 31 May 2005 19:07
While I was trying to find a workaround for another thread, I stumbled
into a png problem I never was aware of:
links don't work when the filter:
progid:DXImageTransform.Microsoft.AlphaImageLoader is used.
So what? People seem to use this filter for ambitioned projects.
On
http://www.daltonlp.com/daltonlp.cgi?item_type=1&item_id=217
I read the links problem can be solved when you add
a {position: relative; }, maybe combined with z-index.
(or use an very small png image).
I found that it works well with the a-posrelative-hack as long as the
filter is not applied to an a.p. element.
see the first test on
http://www.satzansatz.de/cssd/tmp/alphatransparency.html
The links don't work when they are placed above a region where the
transparency is not full.
I had to move the filter from this a.p. element to a layout,
non-positioned child to get the links to work, in this case, the ul
(second test)
(Of course, alternatively, we could build two independent a.p.
containers, one for the image, one for the links, and overlay them.)
I think it's not a z-index-related problem because I can give the links
their own background, which can be seen above the transparent png, but
the non-transparent regions still won't work.
Funnily, /they/ write on MSDN that the text under the image element can
be accessed on full transparency. But why does this stupid hardwired
engine not work when the links are above the image?
So, before I dismiss this silly IE problem, does anyone have an idea how
to solve
a.p.element with filter AlphaImageLoader transparency
+ _child_ links
or can share experience or show the point I am missing?
Ingo
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/