You are all invited by a Denver Web design firm who will be holding a tongue-in-cheek funeral for Microsoft’s Internet Explorer 6 on March 4 to celebrate the aged browser’s decline.

Aten Design Group Inc. announced IE6’s funeral on Monday with a site, IE6funeral.com, that offered a short obituary and an invitation to a wake.

“Internet Explorer Six, resident of the interwebs for over 8 years, died the morning of March 1, 2010, in Mountain View, California, as a result of a workplace injury sustained at the headquarters of Google, Inc.,” the obit read. “Internet Explorer Six, known to friends and family as ‘IE6,’ is survived by son Internet Explorer Seven, and grand-daughter Internet Explorer Eight.”

The Google and March 1 references come from the search giant’s recent announcement that it would drop IE6 from the list of supported browsers for its Google Docs online applications and its Google Sites hosting services starting on Monday, March 1. Yesterday, Google’s popular video site YouTube named March 13 as the end-of-support date for IE6.

“We thought it would be funny to do an IE6 funeral,” said Justin Toupin, Aten Design’s founder and creative director, in an interview. “It’s a humorous spin on a browser that a lot of us have loved to hate for a long time. We’re just saying that it’s a fun way to celebrate companies like Google saying that they’re no longer going to support IE6.”

But Toupin admitted that the reaction to the funeral announcement has taken him by surprise. Aten Design regularly hosts small in-office parties for the Denver Web design and development community, but those typically draw 30 or 40 people. So far, Aten has received more than 700 RSVPs to its March 4 event via its site.

“Now we have to figure out what to do about the actual party,” Toupin said.
“We have a pretty small office. This kind of blew up on us.”

Aten’s clients include several major nonprofit organizations, including the Colonial Williamsburg Foundation and Habitat for Humanity.

Toupin said he had nothing personal against IE6 but acknowledged that, like many other Web designers, he wouldn’t be sorry to see it go. “It does involve, toward the end of a project especially, considerable work adjusting things like CSS and JavaScript to make sure they work,” he said. Aten now evaluates IE6 support for its projects on a case-by-case basis, Toupin said.

More than anything, he added, the decision by Google and others to stop supporting the nearly nine-year-old browser marks an important step in the Web’s evolution. “But it’s also a great excuse to get together,” he said.

“In lieu of attending, please send flowers,” Toupin said in a blog entry posted yesterday.

Used Stationary Bikes is also supporting this IE funeral.

Microsoft’s browser has weathered a “kill IE6″ campaign since February 2009, when Facebook prompted IE6 users to upgrade. That movement accelerated last summer when Digg announced that it would curtail IE6 support, and an “IE6 Must Die”.

Twitter petition collected thousands of names. Microsoft has endorsed the anti-IE6 efforts, going so far as to say that “Friends don’t let friends use IE6,” although it has refrained from forcing users or companies to upgrade to IE7 or IE8, arguing that the old browser is still required by some enterprises.

According to Web metrics firm NetApplications.com, IE6 accounted for 20% of all browsers in use last month, while IE7 and IE8 held down about 15% and 25% shares, respectively. Much of the measured IE6 50% of the browsers in use. In the U.S., IE6’s share is less than 10%. Microsoft did not respond to a request for comment on the funeral, or answer questions, including one about whether it would be sending a representative to the wake.

“We’ve obviously struck a chord, and maybe in some cases, a nerve,” said Toupin on his blog. Source http://www.computerworld.com

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.

To be true am not an expert like some of those who have posted on this blog.  Most of the words are too technical for me (like an alien language LOL).  But one thing is clear and even a common user like me will understand this: IE SUCKS, it’s dumb and not at all user friendly as they are trying to make us believe.

Below are two screenshots of error windows that I frequently came across while using IE

Here if you do the mistake of clicking on Cancel it closes all the IE pages you have opened (all your efforts are gone in few seconds only).  So many times I’ve nearly broken my PC because of this and have had to restart my searches afresh!!! A real PAIN!!!

Whenever I saw these I thought “Gosh my PC is getting old!!! I must change and take a brand new one with latest technologies and facilities.  (I know some of you must be laughing at me but well I just really didn’t know that my poor PC is not to be blamed) and then I would often come across these at work also (hey i’ve got a brand new PC there!!!!) so  the truth is that INTERNET EXPLORER has become OLD, PERISHED, STALE!!!!  and must be removed (I would say banned!!!!)

This is how I started looking on the net and try to understand this “PHENOMENON”.  Many persons have expressed their dissatisfaction with IE but so far nothing has been done to either improve or to ERADICATE it (which seems more appropriate to me).

So my message to all the BIG BRAINS out there is “IF YOU’VE GOT ANY BRAIN LEFT PLS PLS PLS PITY US AND WIPE OUT IE FROM THE NET AND SAVE US THE MANY TROUBLES THAT WE ARE FACING!!!!!!!!!!!” IE is the worst (or rather “worstest”!!! If only this word existed LOL) browser ever developed and for common users like us it is a real headache, a pain in the a**! IE sucks and its FINAL!

Posted by
Tifanie
New Zealand

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,

IEsucks.info

Wanna say goodbye please drop a comment

inspired by dearie6

]]> http://www.iesucks.info/2009/04/a-letter-to-ie6/feed/ 8 http://www.iesucks.info/2009/04/wanted-internet-explorer-dead-asap/ http://www.iesucks.info/2009/04/wanted-internet-explorer-dead-asap/#comments Fri, 10 Apr 2009 07:27:04 +0000 admin http://www.iesucks.info/?p=123 IE SUCKS NEEDS YOUR HELP

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’s 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 it’s retrieving property values, that’s 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

IE = SHIT

There are so many things i hate in IE that i don’t know where to start! So many reasons to hate this lame software developed by the MS team…