Dear IE haters / IE users / Readers,

So far we have been expressing our views on how much IE SUCKS. we have expressed our bad/worst experiences about IE. As Developers and Designers we have shared our opinion and explained why IE sucks!

But we would now like to get the views of our readers… We think its important to know what you people think about it! You are an IE hater? An IE user? Or a fan of IE? Please share with us your surfing experience on Internet Explorer.

IE Haters – Let people know why you hate Internet Explorer.

IE Users – Please share your best/worst experience.

IE Lovers – Come! Prove us wrong!

www.IEsucks.info

It messes up my pages and it’s giving me headaches.
Images won’t load, and text is backwards?
Lame, just lame. I’m not even going to bother with this anymore, and the sad
thing is lots of people still use this piece of garbage, and the
only reason why I’m using it right now is to check the compatibility of my
website. Well forget that.

Hopefully the day will come when internet explorer shit browser disappears and Firefox prevails. Internet Explorer sucks so much, we won’t stop this internet explorer sucks campaign.

XHTML is the future of the web, and the most important part of it is the MIME type used to serve it. Although most web sites are served with the MIME type of text/html, the latest version of XHTML (version 1.1) needs to be served with a MIME type of application/xhtml+xml.

Internet Explorer doesn’t understand this important MIME type, but every other browser does. Safari, Firefox, Opera, and Konqueror are all standards compliant. Internet Explorer is not standards compliant.IE sucks and should be banned now.

So I’m giving my readers fair warning and giving them a mechanism to install Firefox. They’ll be so much better off if they switch as IE sucks and we want it dead.

Yeah, ie sucks, every attempt at DOM based scripting always leads to headaches with IE. CSS scripting is a pain. The market is all IE, so as a web developer, you have to support the damn thing.

I couldnt tell you how many hours ive spent trying to develop something around IE. First, dev it in FireFox (1 hour), then, get it working in IE (2+ hours). Its crazy, i couldnt really care about the security of the thing, leave that to MS to mess things up.

Solution, if you cant get rid of IE because stupid people still use it (and ultimately end up paying more on dev time). then you need a work around. A abstracted layer for dom scripting would be nice. As for the CSS and rendering problems, abstract that away with additional script. Web sites get slower, everyone suffers, angry people throw bricks at MS. Revolution !

After seeing this, you can check out another article by ars technica, which is a response to IE Group Program Manager’s response to people bitching about IE and standards compliance. I found this after building a Web Site in Visual Web Developer 2005 (a Micro$oft product) and having it look perfect in FireFox, only to bring it up in Internet Explorer and having some wierd shit happen. An ASP:Panel changed border styles and text colors (white text was showing up as blue, even if I used #FFFFFF instead of White).

We’ve known each other for 8 years now . We had our good and bad times. Remember those blank night we spend together, you were messing up my css layout and i had to fix it.

Hey buddy i think you had your time , now please leave.

Sincerely,

www.IEsucks.info

Wanna say goodbye please drop a comment

inspired by dearie6

]]> http://www.iesucks.info/2009/04/a-letter-to-ie6/feed/ 9 http://www.iesucks.info/2009/04/internet-explorer-is-dead-and-microsoft-prove-it/?utm_source=rss&utm_medium=rss&utm_campaign=internet-explorer-is-dead-and-microsoft-prove-it http://www.iesucks.info/2009/04/internet-explorer-is-dead-and-microsoft-prove-it/#comments Fri, 10 Apr 2009 10:34:17 +0000 admin http://www.iesucks.info/?p=126 Ask any web designer about IE (Internet Explorer) and you will hear a cringe followed by a grunt and then a few words that we cannot mention on here. Internet Explorer is Microsoft’s web browser and it has caused lot of head aches to many web designers and developers on earth including myself.

Why We Dislike IE and why we say IE sucks?

The biggest problem with IE and maybe with Microsoft as well is that they would rather set some sort of standard even though the rest of the World is using another one that is working very well. In IE this is very apparent and when you design a website, 99% of the time, it will not display the same as any other one of the famous browsers out there such as Chrome, Firefox, Safari and funnily enough its replacement IE 7 and IE 8 (get that for a joke).

So now when you design a site you have to split it into 3 phases.

1. The initial design phase
2. The See if it works in IE phase
3. Then lastly the Fix all the IE issues phase

IE has been found to be the browser that sucks all over the web because of many complaints about its compatibility with web standards and many many other trouble while using internet explorer. IE is violating web standards and now we want it DEAD.

The IE sucks campaign is all about showing the world the troubles of using the web browser IE. There are currently many browsers with cool features. IE renders web sites badly and inconsistently.

Please support the IE sucks campaign and help make the internet a better place by killing the Internet Explorer Browser!

I didn’t have any particular inclination to be nice to Internet Explorer. And I knew I was going to run into bugs and quirks, none of which would be any different in IE7, because the DOM simply wasn’t on the development radar for that version.

Even so, I’ve been nothing short of staggered at the sheer amount of chaotic brokenness evident in its implementation of even the simplest of things.

You wouldn’t have thought it was so hard

In addition to qualifying the value of href attributes on links, IE does the same thing for the src attribute of images.

When retrieving a style attribute, IE returns a style object, rather than an attribute value. Retrieving an event-handling attribute such as onclick, it returns the contents of the event handler wrapped in an anonymous function. Retrieving an attribute value which evaluates to boolean true (such as disabled or checked, when defined) it returns a boolean, and retrieving a value that evaluates to a number (such as tabindex), it returns a number. All of these values are supposed to be returned as strings.

But these attributes are considered by IE to have non-string values; and so if they’re not defined at all they return null, rather than an empty string. IE also returns null for non-defined attributes it doesn’t recognise (ie. custom attribute names).

In its defense, other non-defined but known attributes correctly return an empty string, which is according to specification; and IE is actually the only browser that does this (Firefox, Opera and Safari all return null). But that is not really much of a defense, because it only does that for attributes it recognises, so it isn’t really implementing to specification, it just happens to be correct!

Pure class

To retrieve a class attribute in Internet Explorer you must refer to it as className; to retrieve a for attribute you must refer to it as htmlFor:

//these work in IE, null in others
element.getAttribute('className');
element.getAttribute('htmlFor');

Now this is a side-effect of the mapping of attributes to HTML DOM properties for example, as a DOM property you always have to refer to element.className rather than element.class, because class is a reserved word in JavaScript. But while other browsers reconcile this by allowing string values to getAttribute() to use the original attribute name, Internet Explorer does not:

//these work in others, null in IE
element.getAttribute('class');
element.getAttribute('for');

And there are other attributes that can only be referred to by the camel-cased name they use for their DOM property equivalent, even though those names are not reserved words; I haven’t found a concrete pattern, but examples of this are tabIndex and accessKey.

And there’s more

Internet Explorer implements a second, proprietary argument to getAttribute(), which is supposed to control the way it behaves. The second argument is a numerical flag which can take the value 0, 1 or 2. According to MSDN:

• 0 (default): Performs a property search that is not case-sensitive, and returns an interpolated value if the property is found.
• 1: Performs a case-sensitive property search.
• 2: Returns the value exactly as it was set in script or in the source document.

When it says interpolated value it means it won’t necessarily return a string, as already noted. Notice also how it says if the property is found [my emphasis] this would seem to imply that IE is not using getAttribute() as a getter for node values at all, it’s using it as a getter for DOM properties! If true, this goes a long way to explaining its aberrant behavior if its retrieving property values, thats why it requires property names, and why it returns a value of the applicable type; and when MSDN says that getAttribute() retrieves the value of the specified attribute, it is flat-out lying.

The difference between 0 and 1 appears to be implemented as documented attribute names are treated as case-sensitive, so a search for onClick will not match onclick.

However the value 2 does not behave as documented. When this value is used, event-handling attributes are still returned as functions, the style attribute is an empty string, and values which evaluate to boolean true return 65535 (which is 216, the largest possible value of a 16-bit number. What’s up with that??) But hey on a more positive note href and src attributes do return their literal value, rather than a qualified URI. I suppose we should be grateful for small mercies!

You can see why I said it’s eating my brain, I mean failing so comprehensively to implement the standards is one thing, and bad enough, but Internet Explorer doesn’t even implement its own proprietary stuff correctly!

article source: www.sitepoint.com

• 100% CPU usage;
• accelerators staying active long after I had closed IE;
• Windows XP crashing;
• Settings overwritten – not just the settings I had in RC1, but ClearType, task bar and quick launch were all reset to Microsoft’s default;
• Interference with my Logitech mouse;
• Refusing access to my PC’s localhost, and not keeping the settings for it, so making local testing impossible.