|
Are you saying my simple example didn't work in IE? It works perfectly, here (screenshot attached). If you are doing a number of more complex things, you always have to take into consideration the poor performance of IE, in terms of W3C DOM compliance. One important thing to do is to make sure your DOCTYPE specification is correct. IE will perform differently depending upon whether no DOCTYPE is specified, it's using "quirks" mode, or it asked to be as strictly compliant as possible. Sometimes IE does better with stringent requirements, and sometimes it does better with more relaxed requirements. That's what makes it a pain-in-the-butt. In my last three applications I only had to browser-sniff for one thing, and that was a very uncommon situation involving a div's "table-type" attributes in conjunction with display mode. I was, in fact making rows in a shopping cart disappear and reappear according to use and mode (cart/catalog). IE doesn't always interpret the container hierarchy correctly, in terms of what is parent and what is child. It can truly be a pain in the butt. One has to either dig out all the relevant facts, avoid some particular requirement, or put IE in a garbage disposal and giggle insanely as it goes sewer-bound.
|