IE7 Beta: First Impressions
Wednesday, Microsoft made the first beta release of Internet Explorer 7 available to partners and MSDN subscribers. I've been keeping up with Chris Wilson and the other developers at the IE Blog, and I've been doing my damnedest to give them the benefit of the doubt. I was starting to get excited at the prospect of an IE release that took substantial steps toward compliance. I was all of a sudden an IE Optimist...
Installation:
When I first installed the app, I was greeted by the questionably titled "Microsoft Genuine Advantage" verification system. Sound familiar? Since Microsoft didn't exactly publicize this particular feature, the first time many will have heard of it is when someone figured out how to crack it within 24 hours of it's debut. Having legitimate software and wanting to know more about the experience than the avoidance of it, I went ahead with the process. .. Or at least I tried to. Genuine Advantage tried to open my default browser through which it would validate my software. My default browser is, of course, Firefox, so that didn't work. I was then prompted to download a seperate app, mid-way through my IE7 install, that would be able to validate on it's own. Not wanting to bother with that nonsense, I pasted the URL from Firefox into Maxthon and finished validation.
When I finally finished the installation process, I learned that it would require a full system restart. That means two things: poor user experience, and obtrusive browser OS integration. Wondering what I'd gotten myself into, I restarted.
Rendering:
Bootup took an extra minute or two as I watched a dialog window saying things like "Desktop Update". I knew was that I was getting a gang of "features" I did not sign up for, but I was still excited to see what this new rendering engine could do. Before I could test it, though, I had to open the browser, which involved several minutes of watching it flicker epiliptically on my screen. "Still in beta," I could hear Chris Wilson explaining in my head. When that was finally done I opened up this very blog. Due to an IE6 z-index problem, the tabs on my right sidebar currently have a white border between them and their content. I was disappointed to see that IE7 had not repaired this problem. In addition, the first paragraph of each entry, the first line of that paragraph, and the first letter of that line should have special type treatments, thanks to the CSS2 :first-child, :first-letter, and :first-line pseudo-selectors. These were also unsupported.
I was starting to get annoyed, so I opened Trillian so I could complain to my friends. I got a dialog that said Trillian was crashing at startup. Several more tries and a system restart later, I realized that it was the Trillian MSN Messenger plugin that was crashing, do to some part of the IE7 installation. I managed to disable the plugin and get Trillian running again, but now I can't use it to speak with MSN users.
Impressions:
Beta or not, this is ridiculous. The rendering engine is unrepaired and the app itself is more obtrusive than ever. Having won their latest court battle, Microsoft announced that IE will now be a "feature set" in Windows Vista. Not a standalone app, not a packaged app. "Internet Explorer" will be the name given to the ability of Windows to view internet content. IE is going to be with us for a long time.
Epilogue:
To be fair, IE has made several important improvements, including supporting :hover on all elements, supporting PNG alpha transparency, and showing up late to the HTML 4.01 party with <abbr>. This is all well and good, but these should never have been issues in the first place. Neither should any of the other "improvements" touted so proudly at the IE Blog. These are bug fixes, not enhancements, and there aren't enough of them to make running this bloated clusterfuck worth running. Browse Happy, everybody.
Update:
Just thought I'd chime in and mention that I'm currently unable to run IE7 at all, it just keeps flickernig and not allowing me to focus or select anything. Good thing there are still other options out there.




Comments
You seem to have missed the point of my last blog post - Beta 1 does NOT have any but a couple of our rendering engine improvements in it.
Chris Wilson [MS]
August 1, 2005 09:48 AM
Which couple?
I only tested two CSS bugs here and one of them is called out explicitly on your blog as being repaired (CSS2.1 pseudo-selectors including first-child, first-line, and first-letter).
Beyond that, I looked into z-index inconsistancies that really should never have been an issue in the first place. When I have some time, I'll look more closely at your list of Beta CSS repairs and test them individually, but for now, you're 0 for 2.
Kudos on your vocal support of CSS and HTML standards. I'll look forward to see the proof in the pudding when this thing goes gold.
jason
August 1, 2005 11:23 AM
So, you've had how many years to fix this stuff? And your beta has "a couple of our rendering engine improvements", and two icon bars at the top that I can't move/remove/put anything above?
With all they hype and the horrible lapse of innovation with IE for all these years I think we we're all expecting some serious standards compliance and massive innovation, but instead it's a revamped user interface devoid of the most basic user interface principals and a few "rendering engine improvements"?
Forgive us for not being impressed.
Kevlar
August 1, 2005 11:28 AM
Ok I'm a total lamen here with this stuff but I took a look around browsehappy.com for the heck of it. i am successfully creeped out by ie and downloaded firefox. this prompt is a little slow but this site does look better now. i cant believe ie cant support that. thanks J
Melissa
August 2, 2005 04:01 PM
Unfortunately, I also cannot open **** with IE7 Beta 3. Which is really preposterous the way IE7 Beta 3 is prominently displayed on the Microsoft home page to entice users (not developers or techies) to download it.
When I first tried to install it, not only wouldn't it install (tried first to install to my H: partition and was unable to unlock registry entries) but it removed the XP SP2 settings of IE6 and rendered it inoperable. So inoperable that System Restore would not restore the old settings.
There is no excuse for releasing this piece of rubbish as a finished product (which, in essence, is being done by advertising its availability on the MS homepage), and I dread when this is pushed as an automatic update at the end of the year.
Firefox has my vote now as well...
Charles
August 1, 2006 03:44 PM
Leave a Comment