Forum Moderators: open
Link for XP SP2:
[microsoft.com...]
It's also available in different flavors for Windows Vista, Windows Server 2003 and 2008
Let's see how they come true on their promise to be fully standards compliant.
Release notes are in KB949787:
[support.microsoft.com...]
- John
Some notes I've taken thus far...
- CSS3 Selectors Test
IE7: 329/578
IE8: 334/578
- Focus pseudo-element now supported!
- Styled select elements!
- Standards compliant opacity not yet implemented.
- application/xhtml+xml not yet implemented.
Expect a court case later on for Microsoft abusing their browser monopoly to expand into blogging and maps software.
The whole Acid test thing looks like it was just a piece of marketing so they can push this new browser onto everyone.
[edited by: engine at 12:46 pm (utc) on Mar. 6, 2008]
[edit reason] language [/edit]
Is there an SP2-X64 version available?
[microsoft.com...]
[edited by: swa66 at 6:16 pm (utc) on Mar. 6, 2008]
1. what's so bad about IE7 that IE 8 has to come out so soon?
2. why should we continue to use IE when they keep replacing it and breaking sites?
FireFox all the way for me.
What happens when they get to version 10? Will they land in the marketplace with a 'bang' or a 'thud' when they claim "We're the first Multi-Billion dollar company to come out with a Double Digit browser". That's it. Just change the name from IE to DD, which we can affectionately call Double-D.
And NO, I'm not being sexist with that comment. :)
But I'm certainly not leaving my trusted FF.
Ok, can someone fill me in? Didn't IE7 just come out? They are already replacing something they released in October of 06 and forced on Feb 12 08? Why? What is so important about IE8 that they couldn't just patch into IE7? Two questions:
1. Firefox 2 was release Oct 2006 as well. Are you saying you don't want firefox 3 shortly?
1. what's so bad about IE7 that IE 8 has to come out so soon?
Competition for Standards Compliance for a change. Good Thing [TM]
2. why should we continue to use IE when they keep replacing it and breaking sites?
Not sure what your talking about. Every browser has broken something in all their release glories. No one is perfect. IE7 added some much needed functionality to what is an IE6 core. IE8 is a much needed rendering update/compliance/compatibility update and incorporates many of the features that Firefox is adopting from its own core partners.
FireFox all the way for me.
I like firefox, but there is no reason to hold firefox to a lower standard than its competition. I'm not SOLD on IE8 either, but i don't find it a BAD thing like yourself.
What is it about Korean and Asian sites that is a problem for Firefox?
It's not quite as bad in Japan and China, but there are still sites that I can't seem to get working right in anything but IE. They sometimes have site specific plug-ins and the like, but it's nowhere near the level you get in Korea.
It was reassuring that my own sites were not screwed up by this new version and that I won't have to go through any songs and dances to have them appear properly. Unfortunately, that won't be the case for a lot of others and I will definitely feel their pain.
Here's a quote from libpng.org (the second link above)
full alpha support as of version 7.0b1... inconsistent/broken gamma supporthandles PNGs with gAMA chunks differently (inconsistently) from HTML and CSS colors, from unlabelled images (GIFs or PNGs), and from PNGs with sRGB chunks (see 7.0b1 screenshots)--apparently uses display-system gamma of approximately 1.93 instead of 2.2 (i.e., colors appear slightly dark)
For many uses this is major progress, but there are still limitations -- especially when combining png graphics with IE filters.
There is a meta tag that you can use to force the browser to use "shortcuts" for IE6 and 7 vs. the user having to figure out "I need to click on Emulate IE7".
The biggest help will be for .NET developers esp. those using VS 2008. You were right in the firebug copy...they have had a Developers Toolbar for IE from at least IE6 that allowed you to look at cookies etc. The biggest problem has been debugging client side javascript which has gotten a little worse with AJAX add ons for 2.0 Framework. Exponentially worse with the release of Silverlight 2.0 beta 1 (silverlight 1.1 in alphas...same base though).
Its really geared towards the Blend/Expressions/XAML/Silverlight development that they are pushing. Yes it just conveniently happens that following standards makes that much easier. Go figure but they are at least making an attempt at getting on the band wagon.
thoughts?