main
Report a problem

Microsoft drops hints about Internet Explorer 8

Tom Warren   on 03 May 2007 - 09:40 · 22 comments & 8715 views

Advertisement (Why?)
At the Mix'07 conference in Las Vegas—Microsoft's annual event for web designers and developers—the spotlight has largely been on Microsoft's Silverlight platform, formerly known as Windows Presentation Foundation/Everywhere. Silverlight is a set of tools for developing rich, Flash-like web applications. Less talk has focused around the web browser that will provide the primary user interface for all this new technology. On the Internet Explorer blog, Chris Wilson hinted at some of the things that might be coming in IE 8, while declining to give specific details.

While details may be lacking, the structure of the conferences planned for Mix'07 gives a few hints. Improvements in RSS, CSS, and AJAX support are all being given high priority. It is also widely speculated that IE 8 will include support for microformats, small tags embedded in HTML code that can be interpreted in various ways by software, such as calendar events or contact information. Microformat support is scheduled for Firefox 3, so IE 8 will have to include them in order to keep up. The new version may also include more options for user interface customization, as that was one of the biggest criticisms of IE 7, and one which the developers often blamed on lack of time.

View: Ars Technica

Post a comment · Send to friend Comments · There are 22 additional comments
(4 replies) #1 The_Decryptor on 03 May 2007 - 09:56
"Improvements in RSS, CSS, and AJAX"

Like? Is it finally going to be upgraded to support some of the same stuff other browsers do?, it's lagging massively far behind.
#1.1 Long on 03 May 2007 - 10:09
For the general user, IE7 is an adequate alternative to Firefox.
For pro and enthusiast users, IE7 lacks in customizations and extension capabilities.
#1.2 GoatOfMendez on 03 May 2007 - 10:26
Quote - (Long said @ #1.1)
For the general user, IE7 is an adequate alternative to Firefox.
For pro and enthusiast users, IE7 lacks in customizations and extension capabilities.


Try avant www.avantbrowser.com is it a shell for the IE7 engine and has custumisations for everything. It's the fastest browser in the world.

regards
#1.3 Jugalator on 03 May 2007 - 10:46
Quote -
It's the fastest browser in the world.

Cool, that makes it the second one to be!

Seriously, Opera has long been claimed to be the fastest one out of the major browsers, and this test seem to confirm that at least for Windows: http://www.howtocreate.co.uk/browserSpeed.html

Granted, IE 7 is compared in beta 3, but I'm unsure if performance improved since then. IE was at a very late stage in development then. And... of course, an IE shell will still use IE's advantages and shortcomings in rendering speeds. Also,
Quote -
From a humorous perspective, it is interesting to note that IE on Windows is slowing down, in the majority of tests. Browsers that use the underlying IE engine (Maxthon or Avant, etc.) generally make IE slower, although Avant manages to make an increase in scripting speed.
#1.4 +Dakkaroth on 03 May 2007 - 20:15
Quote - (GoatOfMendez said @ #1.2)
Quote - (Long said @ #1.1)
For the general user, IE7 is an adequate alternative to Firefox.
For pro and enthusiast users, IE7 lacks in customizations and extension capabilities.


Try avant www.avantbrowser.com is it a shell for the IE7 engine and has custumisations for everything. It's the fastest browser in the world.

regards


Avant was good back before there ever was a Firefox. :/
#2 Lastwebpage on 03 May 2007 - 10:21
Can someone explain me the sense of the words "improvement", "more",..., compatibility to standards?
Why not "nearly fully" or something like this? I see no benefits when I can delete a IE Check for Line 10 but must still leave it for line 12 in the source.

On the other side I fear that MS overload the IE with senseless features, let the users choose what they want or not with plugins. Maybe make better some improvements for the plugins to change/add things to the IE UI.
(3 replies) #3 HawkMan on 03 May 2007 - 10:44
unfortunately full compliance won't help.

since so many sites run by what Id' call idiot webmasters are being coded wand tested only for FF now, not following and complyign with standards but instead complyign and following FF. What they previusly complained that MS did... doign the opposite doesn't help their cause.

this is painfully ovius if you use Opera and come across one of these sites with the huge "Best viewed in firefox" logos, you can almost guarantee they have bad coding and doesn't comply to standard and stuff doesn't look or work well in Opera. Stuff that otherwise would work perfectly well if they followed the standards.

some sites, like Google, actually go as far as breakign compatibility for other browsers. Google docs used to work perfectly fine in Opera. Then all of a sudden the document writer app only works half way, and their spreadsheet doesn't work at all...

I'm usually not one to see motives behind things, but they couldn't break compatibility with IE, sicne it is still being used by the majority. but who cares about the Opera users, and if they stop usign opera they're more likely to use FF than IE... and Google is a supporter of FF. ..
#3.1 Lastwebpage on 03 May 2007 - 11:41
Yes, some FF site developers make me really mad...
On the other side, if the only benefit that I have with IE8.0 only another browser to check for, and I must still use some tricks for FF, Opera and IE7.0 this make not really sense.
#3.2 LaXu on 03 May 2007 - 12:55
Usually it seems to be bad JavaScript that breaks in Opera. But IE's JS implementation is a bit ****ed up too. For example IE seems to sometimes interpret variables with similar names as objects. For example "variable1" and "variable2" could be interpreted as "variable.1" and "variable.2" by IE even though they're not objects at all. IE also doesn't work very well with the Prototype framework so I hope that JS is improved as well.

FF is certainly more lenient when it comes to coding than Opera. For example a friend of mine had a mistake on his website where he had forgotten one > to end a tag for a div and it still worked fine in FF but not in Opera. Something like that shouldn't work at all in the first place so people would write HTML that is valid and thus more likely to work in all browsers.

The only things I fear is that IE8 will be Vista only and that by the time it's out it will be a generation or two behind FF and especially Opera. Then it'll again be a situation where web developers are held back by IE's limitations.
#3.3 +Dakkaroth on 03 May 2007 - 20:22
Quote - (LaXu said @ #3.2)
Usually it seems to be bad JavaScript that breaks in Opera. But IE's JS implementation is a bit ****ed up too. For example IE seems to sometimes interpret variables with similar names as objects. For example "variable1" and "variable2" could be interpreted as "variable.1" and "variable.2" by IE even though they're not objects at all. IE also doesn't work very well with the Prototype framework so I hope that JS is improved as well.

FF is certainly more lenient when it comes to coding than Opera. For example a friend of mine had a mistake on his website where he had forgotten one > to end a tag for a div and it still worked fine in FF but not in Opera. Something like that shouldn't work at all in the first place so people would write HTML that is valid and thus more likely to work in all browsers.

The only things I fear is that IE8 will be Vista only and that by the time it's out it will be a generation or two behind FF and especially Opera. Then it'll again be a situation where web developers are held back by IE's limitations.


Man, even when you do code in valid HTML or whatever lang you're using, there's always something I have to go back and work with to make them look the same. As of now, I've given up spending hours debugging one code to have both browsers show things correctly. I just use a piece of JS to tell whether the user is browsing with FF or IE, and have it run separate stylesheets and such. It's a lot faster and easier to do.

I'd love to move to the new IE, but until IE8 can fix the problems left in IE7 and make it more customizable, I'll be sticking with Firefox. And Opera.. ugh.. quick as it may be, I just can't grow to like it. I could go on with reasons, but I think this post is long enough.
#4 bradavon on 03 May 2007 - 11:50
The Avant and Opera UI's suck big time, especially Avant. They're awful and it's like going back 10 years in computing.

Firefox all the way. Agreed IE7 while vastly better than IE6 (which really does look like Win3.1 computing) is still far behind FF's capabilities.
(3 replies) #5 RealFduch on 03 May 2007 - 12:13
Quote -
small tags embedded in HTML code that can be interpreted in various ways by software, such as calendar events or contact information. Microformat support is scheduled for Firefox 3,

OH NO!!!
Doesn't anyone see Mozilla pushing their non-standard proprietary "extensions"??
#5.1 david13lt on 03 May 2007 - 13:43
Maybe... As I remember Mozilla added XUL and now it's cross-platform too. And now we all love it...
#5.2 HawkMan on 03 May 2007 - 17:09
... frankly I hate seen much un.love for XUL, the most laggy resource hogging UI framework thingy ever created.

Why they needed to make it I don't know, there are allready very effective cross platforms system comparable to XUL. though maybe not many based on XML, but I'd rather take a speed gui and less resources over pretty GUI code.
#5.3 Angel Blue01 on 03 May 2007 - 20:02
What do you mean?

Microformats were not invented for use in any partiuclar borwser. They're just XHTML/XML ways of representing information.

I'm glad that some browser will at last support them.
#6 Maysky on 03 May 2007 - 12:35
The question is, will Microsoft make IE8 Vista only?


---
(3 replies) #7 Twisted Vista on 03 May 2007 - 12:40
Almost certainly they'll make IE8 Vista only!
#7.1 Primetime2006 on 03 May 2007 - 14:09
Quote - (Twisted Vista said @ #7)
Almost certainly they'll make IE8 Vista only!


That's a given already, so no point posting this. IE7 is the end of the XP line for IE browsers.


#7.2 GP007 on 03 May 2007 - 15:26
Quote - (Primetime2006 said @ #7.1)
Quote - (Twisted Vista said @ #7)
Almost certainly they'll make IE8 Vista only!


That's a given already, so no point posting this. IE7 is the end of the XP line for IE browsers.


While that might happen, MS hasen't said anything, and the only thing that will decide that are the user numbers when IE8 starts up. If they still have a strong and large XP user base then IE8 will be for XP as well. Not doing that will be a bad move, and make millions more switch to FF or Opera.

At this point, since IE7 isn't tied to the OS as IE6 and older version have been, the same will be the case for IE8, and this makes it easy to support XP and Vista. The only difference between the two might be a few advanced features and any Vista specific security modes.
#7.3 Nodiaque on 03 May 2007 - 17:36
Quote - (GP007 said @ #7.2)
Quote - (Primetime2006 said @ #7.1)
Quote - (Twisted Vista said @ #7)
Almost certainly they'll make IE8 Vista only!


That's a given already, so no point posting this. IE7 is the end of the XP line for IE browsers.


While that might happen, MS hasen't said anything, and the only thing that will decide that are the user numbers when IE8 starts up. If they still have a strong and large XP user base then IE8 will be for XP as well. Not doing that will be a bad move, and make millions more switch to FF or Opera.

At this point, since IE7 isn't tied to the OS as IE6 and older version have been, the same will be the case for IE8, and this makes it easy to support XP and Vista. The only difference between the two might be a few advanced features and any Vista specific security modes.


You forgot IE7 on xp lack some functionality included in IE7 on vista.
#8 +mrbester on 03 May 2007 - 16:36
  • application/xhtml+xml content type?
  • XHTML2 and XForms support?
  • Proper ECMAScript not this JScript rubbish?
  • Full, complete and correct CSS2.1 and CSS 3 support?
  • A separate rendering engine for crappy pages (like Trident) so a new one can start from first principles without having to deal with legacy Frontpage bibble?
No? Didn't think so.
#9 Nodiaque on 03 May 2007 - 17:34
Hmmm... am I the only one to remember the statement "IE7 will be the last version of Internet Explorer since all other new function that will be develop will be integrated with the OS"?

Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!

Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.

Advertisement (Why?)