The platform preview, downloadable from the Internet Explorer website, comes with a number of demonstrations including those for CSS3 border-radius and selectors. The preview also scores an impressive 578/578 on our CSS3 Selectors Test and an improved 55/100 on the Acid 3 test, with further improvements promised before the final release.
You can skip to the end and leave a response.
a good IE
55/100 is still pretty rubbish considering their current modern rival browsers have been scoring 90+ for years.
Glad to see they’re pushing forward with CSS3 and HTML5 though, but they need to push this browser alot more and quickly and get everyone to upgrade their ie version to ie9 otherwise they’re rivals are still going to be light years ahead.
That’s great news for us finally Microsoft has done something new to beat Firefox. But what about the older version peoples are not interesting in upgrading there browsers. They are still using IE6. I am a front-end developer i am facing lots of problems to make site compatible for every browsers. I think Microsoft should have to do something. Like mandatory updates…
Sr. Web Cum UI Designer
It’s the same thing everywhere… Blind IE bashing. *sigh*
@Rob: whether in terms of performances or standards support, other browsers certainly did not offer anything that good 3 years ago. 3 years ago, Chrome was unheard of, and Firefox 2 was the newest Firefox version around.
@Nick: Serious web developers don’t judge browsers standards support based on the Acid3. Acid3 was started with good intentions, but turned out to be all about buzz, and uneducated users keep clamoring for more Acid3 points. Yay.
@Jorge: the usual thing I keep reading everywhere… Unless you’re not doing it right, or you want to use experimental features (CSS3 and stuff), IE8 shouldn’t give you much trouble at all. The only time I ever needed to add extra specific styling for IE8 was too add filter equivalents to opacity. And to be perfectly unbiased, it really doesn’t look like making sites work with IE9 will require any more work than ensuring your stuff works with other modern browsers. So if you’re sniffing for IE9 when it comes out, as if it were IE6 or 7, chances are that you just don’t get it.
And if you properly learn and understand CSS, you don’t just forget it all of a sudden. Or you have Alzheimer.
Besides, most web developers who still bother that much with IE6 do so either because they really want to (even professionally). Let your site degrade gracefully enough with IE6, and move on. Most big sites have already dropped support for IE6. You don’t have to block IE6 either, just don’t bother with it.
Hm, replying from within IE9 doesn’t seem to work. I tried. Or are messages filtered here?
My opinion. I love it, I still don’t like IE but I love the competition. If they would stop developing IE maybe webkit would become the new IE6. IE6 was good when it was first released. Microsoft just didn’t have competition for a too long time. So I’m embracing that.
The problem isn’t IE6 or IE7. The problem is the users who still use those outdated browsers. IE8 is already doable to develop for, I just miss some css3 and html5 support.
I agree with what you’re saying, I was really impressed with all the improvements in IE8. To the point that in my last project I didn’t have to write an extra line of code for IE8.
I’m just amazed that you actually have to support 4!!! different versions of the same application. I understand 2 or 3 in some cases and it’s not for a long period of time, but 4 versions.
In regards to IE6 support, it’s not my decision to support it or not, and I think it’s the same situation for most of us. I don’t usually work directly with the client, but they just don’t understand the reasons. Besides that, if you see that ~10% of your website’s visitors are coming from IE6, you can’t just let them see the “gracefully degraded” version.
Oh, and BTW I don’t have Alzheimer, I was just trying to make a funny comment but you didn’t get it.
People are proving to be extremely closed-minded about IE. What I find very ironic is that a lot of them say things like, “MS, just stop developing IE!”
That happened. They stopped after IE6. And you see what happened?
Years later, they decided to pick up the pieces and race to bring IE into the future. IE7 is still annoying, but IE8 is a perfectly good browser, even if it’s missing the experimental features. IE9 should be competitive.
A few misconceptions:
-Acid3 has little to do with compatibility. It tests a few edge cases; a sort of wish-list for developers, so that their obscure code works exactly as intended in all browsers. It can be important for high-level cross-browser applications, but you really wouldn’t tell a difference between browsers in a regular web-page.
-Firefox has historically had a fairly ‘low’ Acid3 score, with 71 in 3.0, though the recent builds have brought it into the 90s. The Firefox team has even said something like, “We aren’t going to bend over backwards for it, because it’s not really what we’re trying to do.”
-IE7 is dying faster than IE6, and IE8 is soaking both of them up. You don’t have to ‘support’ IE8 in the same ways as IE6 and IE7, any more than you have to ‘support’ Firefox or Safari or Chrome. Things tend to test pretty well in them, by default. IE9 will be similar.
-There is a non-negligible percentage of users on Firefox 2, Firefox 3, and Firefox 3.5. Nobody is complaining about supporting four different versions of Firefox. Firefox 2 doesn’t support display:inline-block (though it supports -moz-inline-stack). Thankfully, Fx2 is basically dead, but I still know people who use it.
I am old enough to remember when IE6 was the good browser, Yahoo! was thee search engine and Apple was a has been.
ACID 3 is nice to have, but like any synthetic benchmark or test it can be gamed. Also 100% ACID 3 is not guarantee of standards compliance.
A standards complaint IE released on a regular schedule will help us all. Hell of a lot better than letting it rot like they did with IE6.
Pet peeve with FireFox is that everytime I open it, there it installs a new version. They seem to update more than Adobe. By the time FireFox finishes patching, I’ve already found the answer, created the post, or did w/e I was doing in IE. Why I never opened it ever again.
while i’m not particularly happy with msft’s almost piecemeal bit-by-bit development and release process, it is notable progress, and proof the company is buckling to pressure to provide better support for popular features.
@matt nails it though. msft understands now understands that consumers will not use their browser if it can’t support a certain level of quality in multimedia & conventional content. so, its more likely to address user needs than developer pangs :[ @Stifu has a good point. when ie9 is released it becomes msft’s best effort at a fully-loaded browser, so as a designer/developer you need only worry about supporting ie9, well.. and ie8 for cover.
/* Does not Work ie9 */
box-shadow: 3px 3px 2px #000;
/* Works ie9 */
/* Works FireFox */
-moz-box-shadow: 3px 3px 2px #000;
/* Works Chrome */
-webkit-box-shadow: 3px 3px 2px #000;
IE 9 looks great, and I was not expecting HTML 5 support so soon from them, HTML 5 needed to come into play soon and I was expecting Internet Explorer to halt is’s progression, so glad I was incorrect.
CSS 3 support = great, sure some missing features but if they promise more I expect they will cover most of CSS 3 before it’s final release, fingers crossed! :)
I believe IE 9 will be an easy browser to support for, and people worrying about previous versions, well, IE 8 is pretty good with CSS2, and most CSS3 features fail gracefully.
What concerns me is if what I read above is correct, if it isn’t working on XP, which still a high population use, many people will not be able to upgrade, which is a silly move for MS.
I also want to see them rid of IE 6 completely!
@Andre, I think they have come far already. Of course none of the CSS3 *bling-bling* work in IE8, but a lot of CSS3 already work in Mozilla, webkit browsers and Opera without the browserprefix.
Text-shadow, multiple backgrounds, RGBA and HSLA work in Mozilla and webkit and Opera.
Rounded corners works in both Chrome and Opera, but not in mozilla and Safari. I whish thay had done a bit more about this, but when Opera and Chrome agree, it can only be short time.
Opera supports everyone of these *and* box-shadow. Hopefully IE9 will not fail on any of them.
Those are the basic needs in my opinion. And besides using all of them together is demanding a lot from the PC for calculation. Use CSS3 wisely… it is easy to exaggerate.
Ugh, freaking spammers…why is it always the most random effing things they’re posting anyway? At least a couple of them link to sites that were deactivated by Comcast! Haha! Go Comcast!!!
Can’t wait until IE9 comes out, and for Firefox to support the standard border-radius property as IE9 preview and final IE9 will, along with several other things. I’m sure we’ll have that in the next Moz update patch, or not. Who knows? All I know is that I can’t wait for Mozilla to support all the animation properties Arora, Safari, Chrome, and Opera nightlies do. But…I’m patient.
1. IE don’t force updates on their customers – because a large percentage are corporate customers who refuse to spend on IT and have legacy systems which only work on IE6. MSFT have stated x1000 times they want everyone to upgrade to the latest browsers – but if their customers don’t want too – they are not going to force them into it. There is no question MSFT want you to update to the latest – security alone would tell any technology moron the benefits.
2. Stop whining about XP already – its an operating system which is 9 years old. 10 years next year – wtf other peice of software do people use which is 10 years old FFS ? Stop complaining about backwards compatibility for XP and upgrade to Vista or Win7. Win7 is an unreal OS and supports every feature you’d ever need and then some.
3. MSFT did revolutionize the browser because of competition from Netscape. Read your fking history. Netscape was the big competition – microsoft jumped web development forward lightyears and then effectively stopped developing post-dot-com and because of web-standards arguments. Google happened. The web took off – and MSFT was left behind. They are catching up – they accept that.
4. Automatic updates aren’t available due to the control MSFT gives to its customers over browsers. Refer to 1). Forcing automatic updates on Corporates would be a disastrous move for MSFT. SO they don’t do it.
5. IE9 looks promising and hopefully speeds MSFT back into the realms of 2000 when they WERE innovating in the browser space and ultimately crushed Netscape. They got smashed in Anti-Trust cases when they added it to their software and the whole web-development ceased for them. Thats in the past – they are now developing to the future.
6. MSFT should earn to allow users to add IE, FF, Chrome or Safari as an options panel for ANY installation of windows – give users choice instead of “forcing” IE or having a menu “If you select none, IE will be installed.” This is a fair based approached.
My 2 cents
No – just sick to death of IE bashing. Yes, IE6 sucked. But everyone acknowledges including MSFT – but that doesn’t mean they are just going to abandon customers.
I use Google Chrome or FF – but that doesn’t mean our company doesn’t heavily use IE for x-browser testing. Maybe IE9 is the innovation that MSFT need since IE6 in 2001.
Dude, i really looking forward to it… this is really big for something like this, they’d never done like this before.. Hahha.. anyway good luck for them.. And ohh yeah..
I’m gonna try the new Version of IE9 that i havent used IE browser for almost 4 years now.. Well what the heck .. we still need to find a better one, than trying to stick with only one isn’t it. .:)
The test results for IE9 as shown on their website are MUCH LOWER than I get in FireFox (Acid3 test, SunSpider test ). This is contrary to what they lead you to believe. So NO I shall remain with the Fox thanks. Although that said, I shall look forward to the improves JS support as some of my visitors are having troubles with IE and JS.
Coding CSS for a website now – Its a pain!!
It works so beautifully on FF, Chrome and Safari… Now have to tweek it by creating a modified CSS file just for IE.
I read ^ that some one said that IE 9 is focusing on secure browsing… Ahmmm so isn’t FF and Chrome already secure?
Its really funny as at work, and in even call center people are still with Firefox. I think most people stick with the best experience they get, and so far ill stick to chrome and ie.
Oh and not forgetting that some websites are already blocked old versions of IE by redirecting website to a separate page for a warning to upgrade.
I tested pure css / html website that works fine on:
FF / Chrome & IE 8.
Its broken on IE9….
How good would it be if there was a converter which simply generates a CSS file for each browser :D
Yes, I use IE6, IE7 &IE8. Yes, I use Chrome, Opera, Netscape, Firefox, Flock, You name it. Do I start a comment flame war? NO. (Here come the fanboy flamewar starters…) Yes, when it comes to rendering webpages, the comptetitors win. But at least Microsoft is trying! Trident is NOT as capable as WebKit or Gecko, so at least they are trying!
IE9 Sucks Monkey Balls! Why advertise all over the web that it supports HTML5 and css3 standards when it CLEARLY doesn’t! This is garbage just like every other version.
I added a box-shadow: to compliment my existing -moz-box-shadow: and -webkit-box-shadow:
Guess what??? NOTHING!!!
Ok so round two… Chrome renders my border-radius:12px 12px 12px 12px; just fine…
Firefox renders -moz-border-radius:12px 12px 12px 12px; just fine too…
What does IE9 do ??? NOTHING!!!
Garbage! Will someone please email this url to microsoft? http://www.w3.org/