I can now type freely...ahhh.
I installed XP SP2 RC2 a little over a week or so ago. The greatest thing happened as a result though I just realized it was possible. I can now type without any worries in the Address bar in IE that it will not interrupt or move my caret around if my home page loads up in the middle of me typing. No more super fast typing immediately after clicking on the blue “e” and no more 404s after attempting to go to URLs like “soft.comwww.micro.” It's such a beautiful thing I've just sat here for a few minutes playing with the new sense of control and freedom this has given me.
Thank you to Omar for linking to Tony's entry that briefly mentioned this. Life really couldn't be better now.
Comments
- Anonymous
July 23, 2004
Funny how the small things make a big difference huh? - Anonymous
July 23, 2004
Unbelievable difference. - Anonymous
July 24, 2004
eatThat's gr
:) - Anonymous
July 24, 2004
Do you have any idea how many times I've typed le.comhttp://www.goog?
I was thinking about getting T-shirts printed up, and seeing how many people would actually start cracking up from reading it (meaning they actually knew what I meant)
Guess who's gonna go upgrade :) - Anonymous
July 25, 2004
How about the disappearing status bar? Did that one get fixed? - Anonymous
July 26, 2004
According to Tony's post it also got fixed. - Anonymous
August 03, 2004
Finally! - Anonymous
August 12, 2004
Oh sure, they start fixing the problems with IE after I've switched to Firefox and have become perfectly happy with it. Oh wait, IE still needs to catch up with the W3C (not that I've found any browser to be 100%-compliant).
On the bright side, the few times I do have to fire up IE now, I won't go insane with rage when it interrupts me while typing in a URL. Before this fix, my solution was to make about:blank my homepage. This technically isn't a bad idea for several other reasons.
The security fixes are welcome, too, although it would be nice if the next version (IE7?) hosted the CLR and used JScript.NET instead of JScript, which might be good for security. But then I'd want it to host C# as well, and then I'd want other browsers to host C#, and, while Mozilla and Mono could make that happen, I'm not sure that it's a good idea.
This may very well be moot depending on what direction Microsoft takes Avalon. If IE will be able to render Avalon natively (and not using an ActiveX control), then it will already need to host the CLR.