Most people do not have a clue on how
messy the whole dhtml area is, unfortunately,
but understandable, because they do not see
the effort it takes to navigate around various browser
bugs like this one.
The whole DHTML issue revolves around the problem that
Microsoft hasn´t had any intention to fix their browsers for years
no complaints against serious bugs which have been open and documented
for years no security holes as open as the grand canyion, really helped
to get out a serious bug fix release, only security releases.
Thanks to the inroads of Firefox they finally got off their collective
***** and finally are doing something again. Things only can become better.
Sure the other browsers also have bugs, but those are reportable and you
can rely on them being fixed within a certain timespan. With Microsoft
you only can rely on having those issues fixed ones the marketshare of
their vehicle goes down.
A good mixup of various browsers in the end probably would be the most
healthy situation with equal shares among all popular browsers. Lets
hope that the we have a monopoly therefore we dissolve the entire IE
team situation won´t happen again. (That is to my knowledge exactly what
has happened)
Werner
Dennis Byrne schrieb:
Thanks to anyone who helped answer this. I asked because I occasionally get requirements where people seriously don't believe why something so simple can increase technical costs so much.
Dennis Byrne
-----Original Message-----
From: Werner Punz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 17, 2006 07:04 PM
To: [email protected]
Subject: Re: z-order of drop down lists and t:inputCalendar
Dennis Byrne schrieb:
For those of you using t:calendar, you may notice that it hides all
drop down lists on the page whenever the calendar pops up. I was wondering
if anyone can shed some light on why this happens. The last time I had this
conversation with a colleague, I remeber him telling me that with some
operating systems, the drop down list control get it's "own window" and you
simply cannot display another control on top by manipulating the z order.
Apparently this goes back to the early 90's . Can't find anything on Google either.
google for the div over drop down bug in the Internet Explorer, you
basically can only bypass that one by putting an iframe under the div
tag which renders the popup.
All Internet Explorer on Windows versions are affected (except IE7 beta)
the bug has been known for 7-8 years and never has been fixed by Microsoft.
(one indication of the shoddy state the IE is actually in)
The reason for this bug is, that the IE rendering engine uses a mixup of
both self rendered and Windows controls, both run in their own
respective rendering engines and probably also event queues.
It internally then meshes both systems. The problem now is, once
a IE rendered control tries to be on top of a windows control by
manipulation of the z-order, the whole thing fails, due to the different
rendering queues. Putting an iframe on top of that for some strange kind
of reason fixes that, the iframe basically can hide the windows control,
and you can fix the z order that way and put anything rendered by the ie
on top of the iframe.
You can find the fix code for this in many controls of myfaces (I once
did a fixup for that bug in the popup javascript code for the popup
control (shameless plug inserted here), the code there is very generic
and can be recycled with minor modifications into any control )
The main problem with this iframe method is, you should only use it on
the IE, because other browsers namely several Mozilla versions do not
like hidden iframes and basically the page goes haywire over this once
you start scrolling vertically.
