ie 7

Here's how to fix those niggling little IE compatability headaches

[edit_g]

This guy might be onto something:
http://dean.edwards.name/IE7/intro/

[edited by: engine at 2:06 pm (utc) on Mar. 9, 2004]
[edit reason] de-linked [/edit]

[mipapage]

This seems promising, but correct me if I'm wrong, with Javascript turned off it doesn't work, right?

Also, it's IE5.5+

[SuzyUK]

It doesn't work with JS turned off... but it's better than not working at all ;)

and I think, any confirmation?, that the percentage of IE users with JS turned off may be very low, it tends to be web "savvy" people who turn JS off.. and they probably use other browsers anyway ;)..

the whatever:hover [xs4all.nl]behaviour (different person) on its own is cool, even if just to play with.. which I have been already ;)

Suzy

[choster]

It's still in alpha, but at least he has been able to squash it down from 28K to a more reasonable 10K.

A JS-requiring fix is, as SuzyUK notes, better than none at all, though I would note that in many cases, people who browse with Javascript turned off have no choice-- their employer or other institution through whom they access the Internet has disabled it.

[creative craig]

The whole site combats those compatability headaches :)

[mipapage]

I agree with you guys for sure (better than nothing), but it's a touch ironic that CSS allowed us to drop using JS for certain things, and here we are using it to make css work! Oh the things that IE will make us do...

I guess I wonder if I would use this on a clients site. I can't see why not, as long as nothing 'crucial' is involved...

[aeve]

It's a really cool idea, but it's a pretty huge download. I think it would be good to hide the stylesheet from the browsers that don't use it by sticking the call in an ie conditional comment.

<!--[if gte IE 5.5]>
<link rel="stylesheet" src="ie7-html.css" type="text/css"/>
<![endif]-->

I guess the stylesheet itself is pretty small, but why risk confusing other browsers when the package can be addressed.

It would really be great to be able to use all those selectors, but really it just amounts to the same thing as giving the called elements a class for ie. What I would really love to see is a fix for explorer's various float problems and an implentation of all the display properties. But that would probably take another 30k.

Adam

[vkaryl]

Erm. The download link was greyed out?

Sounds nifty - would like to have it to play with....

[vkaryl]

Update: I emailed Mr. Edwards, and this nice man sent me the zip file, which isn't large at all - 12 kb or so.

He did point out that this is alpha code - I would take that as a very loud "CAVEAT EMPTOR!" I don't have a problem trying it out since I have a test-box where it doesn't matter what smashes. Others might like to beware for sure.

[isitreal]

<!--[if gte IE 5.5]>
<link rel="stylesheet" src="ie7-html.css" type="text/css"/>
<![endif]-->

I believe you have to change the 5.5 to 5.5000

[source]http://www.javascriptkit.com/howto/cc2.shtml

Notice how we input the version 5.5- as 5.5000. This four digit definition is called version vector, and is required whenever the version to detect is a subset of an integer.

[DrDoc]

I believe you have to change the 5.5 to 5.5000

No, you don't. In fact, you shouldn't.

5.5 will match 5.5000, 5.5123, 5.5206, and 5.5999... whereas 5.5000 will only match 5.5000.

The release build for IE5.0 is 5.0002 on Win2k...
The release build for IE5.5 is 5.5000...

But what about SP releases? If you want to target all IE5, you should only specify 5 as the version number in your conditional comment. If you want to target all 5.5, you should only specify 5.5 as the version number.

For those that are still confused about conditional comments: [msdn.microsoft.com...]

[isitreal]

thanks for catching that drdoc, so much for flakey websites, I'll have to go to the source from now on.