October 10, 2008 at 11:19 am · Filed under Broken on IE8, Frustrations, Plain Evil, ie8
Anne van Kesteren of Opera Software has updated his post on IE 8 to cover beta 2:
XDomainRequest: Microsoft unfortunately continues with XDomainRequest rather than making changes to XMLHttpRequest as other browsers are doing and as is being standardized by the W3C Web Apps Working Group. (Disclaimer: I am the editor of XMLHttpRequest Level 2.)
Some agreement was made to at least support the same protocol on the server, namely using the Access-Control-Allow-Origin header as per Access Control for Cross-Site Requests. (Disclaimer: I am the editor of that draft too.) However, IE8 only supports * as value for that header, not an origin, e.g. http://annevankesteren.nl (test). Sunava pointed out that was because the W3C WebApps WG was still debating the matter. Here is hoping they will fix the bug as there is agreement on that syntax.
- HTML5 DOM Storage:
localStorage and sessionStorage are now supported. Enumerating through them does not give the results I was expecting (I got “length” and “remainingSpace” back as well, besides the keys) and they still have a remainingSpace member that is not part of HTML5. Given that anything that gives some indication of space is highly vendor specific as it depends on encoding, compression, and type of device, they should really rename it to msRemainingSpace or some such or simply drop it.
IE8 also supports an event named storagecommit that is not part of HTML5 which tells you when the data has been written to an XML backend format IE8 uses. The event object for used for the storage does not expose key, oldValue, and newValue. The url member is named uri and the source member is null rather than a reference to the Window object. Ouch!
- ARIA: Aaron Leventhal recently blogged about how ARIA in IE8 is a pain. (Aaron works for IBM making Firefox and Web applications accessible and is a member of the W3C PF WG which standardizes ARIA.) In short, when IE8 renders in super standards mode ARIA will work as everywhere else, otherwise you have to use Microsoft proprietary syntax. So not only do you need to upgrade your application code to be keyboard accessible and ARIA-enabled, you will also need to upgrade it from quirks to standards mode. Alternatively, you could take the easy way out and lock out other browsers. Not nice.
He did admit that he has “only played around with Internet Explorer 8 for an hour so” 
Courtesy of Ajaxian
September 3, 2008 at 9:04 pm · Filed under Broken on IE8, General, Plain Evil, ie8
After all the IE8 talk about standards and their super duper meta tag mode, etc, etc, etc, it appears the IE8 is not planning to be very standard after all. According to this article page “…many, if not most, pages viewed in IE8 will not be shown in standards mode by default…”
Buried deep into it’s settings (I have to test this at some point to see how difficult it would be for a standard user to get here, IE8 is set to display intranet sites in standards mode by default but not for websites on the Internet. In simpler terms, they want IT people to be happy, since their intranet websites will probably work fine (or at least close to, but most websites will not. What is even more astonishing is that the icon used to express compatibility mode is that of a broken page. As the author clearly points, this can be viewed as the equivalent of saying: standards = bad broken page.
I think we can all agree with Microsoft that standards = bad broken page… only if you are viewing the page on any version of IE since all the other browsers are pretty good at following the standards.
Will Chrome be our savior? We’ll leave that for a future post.
July 12, 2008 at 4:20 pm · Filed under Broken on IE8
And this time we are not the ones to point it out. It is Microsoft who does the favor: http://www.thoughtmechanics.com/2008/07/12/ie8-fail-win/
July 10, 2008 at 3:46 pm · Filed under Broken on IE7, General
Haven’t tried this myself, is not very easy now that I’ve completely crossover Mac and I only use IE to test Websites about once every week, but it seems that IE is a memory thief.
Has anybody experienced a similar issue? We may need to keep an eye about this on the upcoming IE8 since it seems to be a recent behavior probably caused by a patch?
June 16, 2008 at 1:36 pm · Filed under General, ie8
In a strange development and a surprise move, Microsoft has announced that it will halt production of IE8 in favor of Firefox 3.
After careful consideration by the IE8 team they have realized that their efforts are geared better towards improving an already good product than trying to salvage the nightmare that has been the Internet Explorer Browser since it’s conception.
Web Developers all over the world have taken the streets to celebrate. One Developer was overhear saying: “At last I will be able to sleep and eat as a regular human being, I mean I couldn’t think of anything other than IE hacks for almost 6 years. This is a true blessing.”
We will keep you posted as more news developed. So far you can read more about this amazing day here and here.
* Sigh, only in a perfect world.
June 11, 2008 at 8:26 am · Filed under Frustrations, General, ie8
It’s been quiet for a while here on Stupid IE since we’ve been busy doing some better things than worrying about IE and also because we are waiting for the next release of IE8 to see what surprises it yields.
But today, we have been hit with this piece, directly from the Microsoft Blog and we wanted to leave our two cents.
It seems that Microsoft didn’t have enough with creating their Meta Tag but now they’ve decided to create another one which does the same thing but in a different way or something in between. Yes, I don’t understand either but this is Microsoft we are talking about people, nothing is supposed to be understood.
“NOTE: The X-UA-Compatible tag and header override any existing DOCTYPE. Also, the mode specified by the page takes precedent over the HTTP header. For example, you could add the EmulateIE7 HTTP header to a site, and set specific pages to display in IE8 mode (by using the meta-tag with content=”IE8”).
Using the IE=EmulateIE7 compatibility tag is a simple way for users to continue their current experience when browsing your site until you can update with more standards-compliant content. Although adding this tag will prevent most display issues, you may also need to update your site to properly detect IE8. ”
So I can have the tag on the website but have another one on the pages and then this will prevent some, not all, of the issues until my content is more compliant???? So the fact that your browser was not compliant to begin with means I know have to do more work than before??
We are checking into a mental hospital pretty soon. Anyone care to join?
June 2, 2008 at 9:13 am · Filed under Broken on IE8
Simple:
- It doesn’t work correctly: Check here and here
- It is a pain in the ass to go from IE8 to IE7 when needed. “The first beta of IE8 has an “Emulate IE7″ button, allowing users to effectively revert to the old browser on pages that don’t render properly.” Steps are explained here.
May 8, 2008 at 9:39 am · Filed under Frustrations, General
As it turns out, is not only IE8 Beta who’s having a problem with the update. IE7 has join it as well. Yes, I know is not a mayor issue and all that will happen, at least until now, is that you won’t be able to uninstall Ie7 or Ie8 to revert back to IE6.
I have to say that this may have been a good thing and if I were Microsoft I wouldn’t say anything to Ie7 users, this way, I would’ve force them to stay on IE7 and dump the crappy IE6. As a matter of fact I would’ve included IE7 by default on the update so that people started loosing the crappy IE6. But I’m not Microsoft so I’m not that smart.
April 10, 2008 at 7:55 am · Filed under General, Other Microsoft Nightmares
I like this article because it is the first one that I’ve seen in a while that doesn’t suck up to internet explorer 8 by talking about how it passes the acid2 test which it doesn’t.
Now, for the sake of argument I’m going to forget about the little ActiveX issue which causes IE8 to not pass the test and go along the lines that it does indeed passes it. Great, now what? Well for starters, is messing up maps, even some with the Emulate IE7 button turned on, security is still an issue and it’s not offering the level of security firefox is offering and it is even breaking it’s own Mircosoft Websites (I’m sure this one will be fixed very soon but it’s funny to point it out).
On top of this Microsoft hasn’t learned from the past and it is creating browser specific innovations which is one of the main reasons their browser sucks inn the first place. To make my point clearer, by adopting technologies that are only available on IE8, Microsoft is doing three things wrong:
- It’s development team is focusing on the wrong task as they are working to implement this features instead of working to make their browser standard compliant (this website seems to be down but it talked about how Microsoft’s money people were about to drop the idea of making IE8 standards because they thought it was a better investment to offer a set of nifty little features).
- Is creating more of the so called racists websites.
- Is creating proprietary CSS, javascript, Ajax, etc that will only work on their browsers. And even if this is sometime good, after all a lot of innovations have come from browsers doing exactly this, the problem lies on that you should follow the rules first, then go and break them but make them open so that everybody can adapt them.
Yes I know it is just a Beta but as I said before, if IE7 was a step forward from IE6, why don’t you just fix what it had wrong instead of creating something completely new that is breaking even more things than IE6? No one knows.
April 1, 2008 at 4:45 pm · Filed under Broken on IE8
This post is self explanatory. A couple of tests which IE8 fails.
http://www.builderau.com.au/program/css/soa/Comparison-of-CSS-compatibility-on-IE-Firefox-Safari-and-Opera-/0,339028392,339287800,00.htm
Yes I know, it is only a Beta, but so far is not looking good.
Next entries »
