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."
.. it's a sad state of affairs when a developer outside of Microsoft actually ends up doing something that MS should have done themselves. So they can say 'screw it' to standards and someone else does the finger-work.
Is ponder how to get over the Slashdotting of his site.
I'm sure the CSS is a work of technical art; seeing it would be even better.
Donte Alistair Anderson Roberts - hi son!
Karma: Chameleon
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
Fact is that IE 6 doesn't even support CSS2 properly which became a W3C recommendation in 1998.
--
The world is divided in two categories:
those with a loaded gun and those who dig. You dig.
The power of IE is that it's broken but it may be possible to fix it?
I have a powerful car for sale if you're interested.
But this is why FireFox still isn't onto release one. I also get problems on my XP box using some sites, especially forms; but there are also still sites that don't work correctly in any release.
IE has the usual MS philosophy in that if something doesn't comply with the way they've done it, who cares because everyone will change to their way of thinking. I agree with those who don't like that someone else has to clean up after MS but what else are you going to do? For better or worse it is, and will be for a while yet, what most non-techy people use.
Perhaps it's slashdot that needs to be made standards compliant! It would seem that someone doesn't want us to know how compliant it is.
It seems WDG had better luck getting through, but look at all those errors!
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
Flippancy apart, I think using CSS to make IE7 W3C compliant is a really brilliant idea. However, the browser itself is a small part of the equations. Very few websites are W3C compliant. Vast majority of them are geared to a certain browser, depending on the whim and fancy of the designer.
For my part, I run my sites thru Anybrowser to make sure they will render on, well, as the name suggests, any browser.
Nothing to see here
> mozilla was last released yesterday - ie6 was
:-)
> released 2+ years ago
So, you're saying that the problem is not IE but the broken proprietry way of building softwarwe that can't can release new versions in time to answer real customer needs?
I think I agree
Gilad
Gilad.
Anyone who cares this much about the company's product should be given serious consideration for employment.
Microsoft should hire him...
That's pretty sad, for /. to mess with their server settings to disable the w3 validator. Their HTML has been terribly broken for years. I don't understand what they do with all that money they have, because they sure haven't been improving the site very much. Makes me glad I don't subscribe and I block their ads.
Gates' Law: Every 18 months, the speed of software halves.
current project i'm working on i did all css layout (ie; no tables) and had opposite experience: same code was fine in moz / opera, needed completely different version for ie5 and ie6 due to various bugs in each.
now actually reverting to tables for a lot of the layout because of it.
try this one
Ceci n'est pas une
And what's more, it doesn't even fully support CSS1, which was released in 1996! Try the ComplexSpiral demo, which is a neat demo of the effects possible in Mozilla, Opera and Safari with the 'background-attachment:' CSS1 property, which IE supports only on the BODY tag. Also, let's add 'position: static' support onto our wishlist (for watermarks/menus on pages) and PNG alpha support, and a whole bevy of regular CSS rendering bugs that have remained unsolved for years. MS claims "full CSS1 compliance", but in reality they only support the reduced CSS1 core spec.
;).
And to think it'll be a wait of several years before IE is updated with Longhorn... until then, writing pure CSS sites is going to remain a bug-whacking chore. Let's all be collectively glad that MS fought so hard for their "Freedom to Innovate" back in the anti-trust days
P.S. redesign slashdot using modern web standards, editors!
<!-- DHTML / JavaScript menu, popup tooltip, Ajax scripts -->
So I'll ask the burning question here: How is creating a stylesheet to be included in individual web pages considered making IE standards compliant? Wouldn'the the article be more acurate if it read "modifying web site allows it to be rendered correctly in IE6?"
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
Other than that, every other site I use works great in Mozilla, including banking sites and other sites that you'd think would be tempted to make the IE-only mistake.
What I don't miss is the pop-up I used to have to endure in IE when I disabled ActiveX, not to mention it's countless lack of features (tabbed browsing, popup blocking, etc,...).
Open Standards Portal
Remember when Microsoft was releasing and improving IE on a rapid basis? Let's see, when did Microsoft allegedly win the browser war? Oh, about two years ago. When did Microsoft stop innovating IE? Oh, about two years ago. Since then, Microsoft doesn't care cause they have the browser market locked up. Therefore we need to download stuff like this and google toolbars to add pop up blocking and all kind of other third party stuff to get IE up to some modern day level.
Unfortunately if MS continues like it has done, the web will stagnate with no cool new features appearing. MS has made it clear they're not interested in making IE standards complient or adding any new enhancements. Since 95% of people use IE (and probably have no clue that there is anything other than IE available), if IE is never enhanced then web developers will forever be stuck in the trap of never being able to use any cool new features that IE doesn't currently support. Very few web developers will be happy adding features to their website that make it unusable for 95% of their visitors (although it seems that professional web developers have no problem with making their sites only work with IE).
:)
What I'd love to see someone do at some point is re-skin FireFox to look like IE and then abuse one of IE's many security holes to replace IE with the reskinned FireFox on any machine that visits the website.
http://blog.nexusuk.org
The magazine A List Apart has already redone Slashdot's design with web standards. Look here:
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.
Did you hear? McDonald's heard about this move by Microsoft, and was inspired to imitate their strategy. McDonald's is now pushing through the Department of Agriculture to add "Big Mac" and "Chicken Nuggets" to the Food Pyramid, placing them just below the highly-coveted "Dairy Products" block. McDonald's argues that since such a huge percentage of the population is eating their food, everyone should consider their products a nutritional standard.
Man, you need to leave Mr. Shatner alone when he's trying to make a point!
And the muscular cyborg German dudes dance with sexy French Canadians
It is meaningless to comment by saying "hey I use firefox", because the rest of the world is not using it. Now still 25% of my visitors are using IE 5.5, given that IE 6.0 is there 4 years ago.
Yes, it is much easier to make Mozilla/Opera more IE-complaint. [See IE Emu]
It is also quite easy to design a new set of API such that they are deligated to the correct version supported by the browser in runtime. [See DHTMLLib] [See CBE]
But these are just the wrong way.
A patch to IE means:
It is exactly something like Cygwin, which implies UNIX-style programs are correct programs. When you move to Linux is just your choice.
This is an age-old problem for web developers. Good developers test their work in multiple browsers, and should also do a test in browsers a few versions back. This might mean keeping an extra box lying around that runs Windows, or using VMWARE or WINE to run Internet Explorer. People might flame me and say that any good developer KNOWS what the content will look like in different browsers and tries to produce a browser-agnostic design, but experience tells me that there's nothing like a quick test to find your mistakes.
GreyPoopon
--
Why is it I can write insightful comments but can't come up with a clever signature?