Summary of IE Hacks?

[deko]

As I understand it, IE7 is still not standards compliant (although it has
cleaned up some bugs). Can anyone point me to a summary of IE bugs and fixes?
I've recently discovered Conditional Comments, which are supposed to be a
reliable solution, such as this:

<!--[if IE]>
<link rel="stylesheet " type="text/css" href="iestyle.c ss" />
<![endif]-->

This looks like a good way to go - that is, just use a separate stylesheet for
IE - but that begs the question of how to fix particular problems in IE. Is
there a good summary of IE quirks and workarounds someone can point me to?

Thanks in advance.

[rh]

"deko" <de**@nospam.co mwrote in message
news:K_******** *************** *******@comcast .com...

As I understand it, IE7 is still not standards compliant (although it has
cleaned up some bugs). Can anyone point me to a summary of IE bugs and

fixes?

I've recently discovered Conditional Comments, which are supposed to be a
reliable solution, such as this:

<!--[if IE]>
<link rel="stylesheet " type="text/css" href="iestyle.c ss" />
<![endif]-->

This looks like a good way to go - that is, just use a separate

stylesheet for

IE - but that begs the question of how to fix particular problems in IE.

Is

there a good summary of IE quirks and workarounds someone can point me

to?

>
Thanks in advance.

http://www.webcredible.co.uk/user-fr...s-tricks.shtml

http://www.stylegala.com/resources/css_hacks.htm

http://www.quirksmode.org/css/quirksmode.html

nice table of what's supported in each browser (scroll down)
http://www.quirksmode.org/css/contents.html

Lots of css links. Check the "* daily reading" & "css techniques" for
sites that would have info on quirks
http://www.alvit.de/handbook/
Rich

[need help]

depending on what browser youre targeting and developing for, the "other"
browser will always have bugs you need to fix.
for example if as you developed you tested everything in IE and made it
work, then at the end went to test in firefox, you would be asking for a
list of firefox bugs.

will we ever have true compliance across platforms??
"deko" <de**@nospam.co mwrote in message
news:K_******** *************** *******@comcast .com...

As I understand it, IE7 is still not standards compliant (although it has
cleaned up some bugs). Can anyone point me to a summary of IE bugs and
fixes? I've recently discovered Conditional Comments, which are supposed
to be a reliable solution, such as this:

<!--[if IE]>
<link rel="stylesheet " type="text/css" href="iestyle.c ss" />
<![endif]-->

This looks like a good way to go - that is, just use a separate stylesheet
for IE - but that begs the question of how to fix particular problems in
IE. Is there a good summary of IE quirks and workarounds someone can
point me to?

Thanks in advance.

[Beauregard T. Shagnasty]

need help wrote:

depending on what browser youre targeting and developing for

Isn't the answer to not target and develop for any particular browser?

--
-bts
-Motorcycles defy gravity; cars just suck

[Ben C]

On 2006-10-16, need help <[e-mail] :

depending on what browser youre targeting and developing for, the "other"
browser will always have bugs you need to fix.

for example if as you developed you tested everything in IE and made it
work, then at the end went to test in firefox, you would be asking for a
list of firefox bugs.

Not if "making it work" in IE consisted of writing incorrect content
either consciously to work around the bugs or because you were in a grey
area between knowing clearly what was supposed to happen and just trying
anything that would work.

will we ever have true compliance across platforms??

Firefox, Opera and to a slightly lesser extent Konqueror in my
experience all come very respectably close to standards compliance, and
it's pretty rare to come across bugs, especially in FF or Opera.

[Gus Richter]

need help wrote:

depending on what browser youre targeting and developing for, the "other"
browser will always have bugs you need to fix.
for example if as you developed you tested everything in IE and made it
work, then at the end went to test in firefox, you would be asking for a
list of firefox bugs.

That way will get you into a load of trouble.
Write it and make sure it's as you want it in Fx and *then* check in IE.

--
Gus

[deko]

depending on what browser youre targeting and developing for, the "other"

browser will always have bugs you need to fix.

It would be a tragedy if each browser required its own stylesheet.

will we ever have true compliance across platforms??

Probably not. But IE appears to be the only real pariah at the moment. And
until MS chooses to make IE standards compliant, web developers have to deal
with it.

What I like about Conditional Comments is that only IE reads them (a supposedly
reliable feature of IE, including IE 7). So there is no additional overhead.
The size of a standards-compliant stylesheet need not be bloated with IE hacks,
and visitors smart enough to use standards-compliant browsers are not penalized
in any way.

So, maintaining an IE-specific stylesheet like this:

<!--[if IE]>
<link rel="stylesheet " type="text/css" href="iestyle.c ss" />
<![endif]-->

is, IMHO, the cleanest and most effective way to manage the display
peculiarities of IE. An iestyle.css can contain every hack and workaround to
accommodate each IE version (all the way back to IE 5), all cordoned off the
side, where they belong.

[deko]

>Is there a good summary of IE quirks and workarounds

>
http://www.webcredible.co.uk/user-fr...s-tricks.shtml

Thanks, the webcredible site is helpful.

I also found this, which I thought was pretty good:

http://www.communitymx.com/content/a...ge=1&cid=C37E0

[Martin Eyles]

"deko" <de**@nospam.co mwrote in message
news:o8******** *************** *******@comcast .com...

>
So, maintaining an IE-specific stylesheet like this:

<!--[if IE]>
<link rel="stylesheet " type="text/css" href="iestyle.c ss" />
<![endif]-->

is, IMHO, the cleanest and most effective way to manage the display
peculiarities of IE. An iestyle.css can contain every hack and workaround
to accommodate each IE version (all the way back to IE 5), all cordoned
off the side, where they belong.

Do you mean something like this

/* Hacks for all IE - including IE7 */

.... {}
.... {}
.... {}

/* Hacks for IE6 and before */

* html ... {}
* html ... {}
* html ... {}

/* Continuing with hacks for IE5.5 and below */

and so on...

If so, I like the approach - better than having lots of sets of conditional
comments. Might use that in the future if I need to hack IE7 and IE6
differently (although I will probably ignore IE<6 - it tricky to test, and I
don't think quite so important).

Martin

[deko]

>So, maintaining an IE-specific stylesheet like this:

>>
<!--[if IE]>
<link rel="stylesheet " type="text/css" href="iestyle.c ss" />
<![endif]-->

is, IMHO, the cleanest and most effective way to manage the display
peculiaritie s of IE. An iestyle.css can contain every hack and workaround to
accommodate each IE version (all the way back to IE 5), all cordoned off the
side, where they belong.

Do you mean something like this

/* Hacks for all IE - including IE7 */

... {}
... {}
... {}

/* Hacks for IE6 and before */

* html ... {}
* html ... {}
* html ... {}

/* Continuing with hacks for IE5.5 and below */

and so on...

yep.

If so, I like the approach - better than having lots of sets of conditional
comments. Might use that in the future if I need to hack IE7 and IE6
differently (although I will probably ignore IE<6 - it tricky to test, and I
don't think quite so important).

Yeah, I don't see much IE 5 anymore...

This approach seems like the best solution to me. Still waiting to hear what
others think...