IE8 – something behind the IE blog’s evasive post?


There’s been a lot of jokes and angry comments about how, the IE blog (the official Internet Explorer blog), is being pretty mean/dumb for putting practically NO useful info. about the upcoming IE8.

No new icons, no specific new features, no upcoming dates, NOTHING.

All the techie Firefox users are saying IE8 will be just a joke, like all the other previous IE browser (though I like IE7). Some avid users are being pretty frustrated, because they want to know more, but Microsoft, who’s usually has more open bloggers, isn’t spilling anything.

So that brings in a question : Does the IE blog’s silence mean that there’s really something new going on for IE8?

Couldn’t there be the possibility that Microsoft has finally learned, and realized that the must give IE8 anything imaginable to pull ahead of the ever-growing Firefox, in order to stay one of the top browsers?

Yep. I think it is. Though I’m usually an optimistic person, and look at the glass half full. But why assume the worst? There’s nothing at all that indicates that the team’s silence, means they have nothing.

Here’s what I think : Microsoft knows that it’s been neglecting IE for awhile, and not putting anything that would make it truly better than some of the other browsers. So now they’re making up for lost times, by making sure that IE8 will be a browser to love. A browser to appreciate it. A browser that’s wanted. Or ELSE, if the next IE8 only fixes things that should have been there, and minor new features, well Microsoft can say goodbye to it. I know I will.

So Microsoft is really picking up all the slack from all these years, and are now working to make IE8 the best. Things that matter to developers, users, and everybody all alike, like:

  • flawless CSS 2 support
  • CSS 3 support per drafted specs
  • HTML 5 per WHATG/W3C draft, including [canvas]
  • script debugging registry hooks that are no so easily corrupted
  • coordination with Silverlight team to facilitate full W3C DOM automation (and window.eval()-esque interopability from Silverlight to browser script runtime) from Silverlight runtime
  • optional browser-based script debugging
  • inline XHTML extensions (as per the spec!!)
  • Full 2.1 and CSS 3 ‘box-sizing’
  • faster phishing filter
  • zoom scaler like in Office 07′
  • spell check
  • Tab History
  • separate buttons for Favorites, Feeds, and History
  • More official free add-ons
  • A better add-on site
  • Skins!!!
  • flexibility of Firefox
  • Speediness of Opera
  • Better mobile IE8 that can do many of the main tasks as the desktop version
  • Like everybody says, COMPLETE WEB STANDARDS. Not the ones Microsoft thinks is right.
  • Red/yellow/green address bar to tell of the site’s level of danger to you
  • A pop-up blocker, that allows new windows to show up if YOU actually press on the link 2 or more times. If I press it so much, I want it, duh.
  • Screen Clipper – takes a clip of the page you’re viewing, easy to crop it the way you want it, and copy & paste somewhere
  • Better look in XP – IE7 with AERO was awesome in Vista, but with no AERO and ugliness in XP
  • Less crashes

Like I said, IE8 would need some more edge besides these bullets. Something really new.

So I have some high hopes for IE8. I’m really expecting Microsoft to go over the top to ensure their place in the market.

So I’m going to be the optimistic person, and hope for the best.


2 thoughts on “IE8 – something behind the IE blog’s evasive post?

  1. Browser development, especially with regards to standards compliance. Part of the whole mess has to do with the fact that, especially early on in the Web would, people authored pages that were not compliant to the markup specs. Browsers, when faced with a page like this, have two options: (a) refuse to display the page, since the page isn\’t compliant, or (b) put up with the bad markup and display the page despite its refusal to adhere to standards. As it turns out, option (a) is not reasonable, because doing that will break many sites with bad markup. The only real option is (b). The problem is that option (b) means that the browser has to go around its own compliance rules to make bad pages display. I urge caution with your compliance statements – it\’s not as simple as you think. Are you willing to build a browser that throws out non-compliant markup?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s