Slashdot Mirror
Making IE Standards Compliant
spin2cool writes "Dean Edwards has taken it upon himself to make Internet Explorer W3C compliant. How? Well, it isn't by patching the application, as you might suspect. He's created a stylesheet, dubbed 'IE7' that uses DHTML to load and parse style sheets into a form that IE can understand. Just include the style sheet in your HTML pages, and things should render correctly. The complexity of the CSS transformations is really amazing and shows off the power of this stuff."
I wish someone would release such a sheet for firefox : /. itself still doen't render correctly on FFox 0.8 under XPpro. As shown here, the left column tends to dribble into the article summary...
When will I end this grieving ? When will my future begin ?
Site is already slashdottet. Here's Google's cache of the document.
So - how are the plans going with implementing a slashdot cache?
Underholdning.info
If you havent already yet, you should of switched from IE to Firefox. It is now my default browser on Windows, and on Windows XP it even puts it as the top Start menu item. It is fast, light, small download (6Mb), Tabbed Browsing, Popup blocking, Download manager, Cute icon and standards compliance are all good reasons to use it. So don't use an ugly hack to transform your pages for IE, put a firefox icon on your site.
So if you havent downloaded it yet, get it now!. Avalible for Windows, Linux, Mac OS X and more!
found here
AFAIK there is no browser available that correctly renders CSS 2.0 -- the entire spec.
IIRC Moz and Opera do render all of CSS 1.0 correctly and nearly all of CSS 2.0 correctly. But doing some advanced things with CSS 2.0 (especially doing all formatting with it, instead of old table hacks) you really run into problems with both Moz and Opera.
Use a Mozilla Firefox nightly build, the bug (217369, I think) that caused this problem is fixed in them.
More major changes since 0.8 here.
"You should never doubt what nobody is sure about." -- Willy Wonka
The title of the news is misleading : this JS component only corrects some CSS 2 selectors that IE doesn't natively support.
So it doesn't really make IS standards compliant, it just extends some functionnality. It doesn't, for example, correct the box model of IE5.
So I'm afraid it doesn't spare us of using CSS hacks to filter out IE.
in reality, they can of course by not using closed source software, but for some it seems percieved convenience is more important than freedom, but I digress)
What this does is allow developers of standards-based sites, which they have under their own control, to provide a stopgap for users who don't understand the issue of standards and so haven't themselves chosen freedom. So your digression doesn't quite match the facts. As a developer, I can choose to make my site work in Mozilla and KHTML - and will - but I can't choose to force my audience to use them. With this, if it works as advertised, I can choose to follow standards and still provide some means for those who have, for whatever reasons, chosen to use a non-free browser to use my content.
I made this mirror based on the Google cache. It has the full source code, as well as the docs he wrote.
This is temporary, of course.
|/usr/games/fortune
try this one
Ceci n'est pas une
You are right, which is why some of the more esoteric features have been removed from CSS 2 and CSS 2.1 is about to be released.
However this is a lot different to Internet Explorer 6's situation. There are massive amounts of CSS 2 that simply aren't implemented, such as a whole bunch of selectors and tables.
The next time you see somebody complaining that CSS layout is hard, remember that there's probably a way to do what they want in a few lines of CSS, but that part of CSS simply doesn't work in Internet Explorer (but does in Mozilla, Konqueror, Opera, etc).
via Google Cache : IE7.htc
The code itself at the moment is 27k, which is kinda hefty for most pages on initial load (though you'd only have to load it once per site). However, it includes loads of comments, which might slim it down to about half that if you stripped them out. And the savings in other code areas by not having to write double-code and browser-detection are probably worth it overall.
:-)
This would certainly make development a lot easier... I look forward to trying it out
Can someone temporarily host my site? some of it is php4. is that ok? mail me at dean@edwards.name and cc 9jack9@msn.com. i can chat on the msn account if necessary. thanks. dean edwards
Just to clarify slightly - IE7 doesn't rely on serving up a different stylesheet, but an additional 'sheet. In other words, if you reference IE7 as your first 'sheet, existing stylesheets for compliant browsers will then render OK in IE.
If I've read it right you don't even need to sniff (well, at least not in the old-fasioned, java-script or server-side script sense): it's all done through CSS.
This is where the serious fun begins.