and so I was sad to see it go away again today:
Y’know, I remember seeing the early web on Lynx, and thinking “oh, like gopher, except harder to use — what’s the point?” Then I saw it on Netscape 1 and everything changed.
(Yes, I actually have a need for NT 4 Server right now. I never thought I’d be installing Option Pack this many years later. At least I’ve got Virtual PC & Server these days).
I’m really not in love with IE or anything, but I do fight with it a lot…
I need to cover what I am in love with: my family, music, ice cream… — the good stuff.
Something I bumped into today: The first time Internet Explorer loads a URL, it sends an “HTTP_Accept” request header with the list of MIME types it accepts, like so:
HTTP_ACCEPT = application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */*
Any subsequent request of the same URL, though, only sends “*/*”:
HTTP_ACCEPT = */*
Of course I watched this through an ASP page which wrote out Request.ServerVariables("HTTP_Accept"). I wasn’t sure if it was IIS or IE‘s fault tho, so I checked the raw headers with Fiddler, and it’s definitely IE.
What’s especially strange is that I can find little or no mention of the problem. Anyone else heard of (or conquered) this?
It rather messes up a page I’m working on…
UPDATE: See here for a bug and workaround demo article I just put together.
Yeehaw it’s out! I’m downloading now and am actually excited to testdrive it. Already noteworthy to me is the functionality changes section in the release notes:
Scriptlets—Internet Explorer 7 disables Dynamic HTML (DHTML) scriptlets, by default. (Scriptlets were deprecated in Internet Explorer 5). They can be reenabled by system administrators, changing URLActions with the Internet Control Panel (INetCPl.) The INetCPL text should read “Allow Scriptlets.” If your programs rely on scriptlets, we recommend that you use DHTML behaviors which are more efficient. Disabling scriptlets is part of our continued work to ensure that unsupported technology is deemphasized in Internet Explorer.
I’m very happy about this. It sounds like Microsoft listened (!) to my request to not remove Scriptlets after all, but to instead just disable them by default (which is certainly a good thing for security). I have several good old IE components written as DHTML Scriptlets, and I need some option to keep using them in existing web apps.
This is a big big deal, and again a good one. But does this include disabling the built-in ActiveX Controls too, like DSOs and XMLHTTPRequest?? (if so, then ouch!) Good idea on the file input, but it sounds like it’ll cause some rewrites.
This surprises me. It may be old tech, but it was big (remember all the “push” hulabaloo? man, those were the [something-] old days), and I do still see sites using it. Not sure from that statement whether it’ll come back in a later beta or RC, tho…
Another big change. So what’s the replacement it, native SVG finally??
Good and better.
Ah, lovely bug fixes. More please!
(actually, I wish I had known about that window.opener trick a long time ago. Darn!)
All sounds good to me. I’ll be a little sad about _search, tho, but only a little.
It actually stopped working back in IE6sp2, which was a pain for me. It was a Netscape standard, albeit de facto, but it was still quite handy for sharing code (and non-abusable, that I know).
Gopher, sure — I haven’t touched that in 10yrs.
The Favorites method — eh, not a big fan, but I’ve seen some very cool specific uses (uploading to bookmark sites, in particular).
But why no telnet://? All that ever did was open the default telnet client. This’ll definitely be a pain for some sites.
I actually have no idea what this is, which is unusual with IE. Anyone wanna enlighten my ignorance?
I wont miss this one much. When I’ve used it, it’s been more a toy or bandaid for ugly URLs. Much more often I’ve seen it abused, so all good here.
I’ll post more if I find my test-drive interesting.
There’s more good discussion about it over on the IEBlog.
Or SELECTed wisely… (ok, so the quote doesn’t quite work).
Considering my frustrations with IE’s buggy SELECT element (dropdown list), or my workarounds for those problems, it should be no surprise that I’m quite excited about IEblog’s news about SELECT element fixes in IE7:
For the SELECT few….
z-index fixed, styles fixed, title fixed. Finally! (But no mention of scripting bugs… hopefully they get those too!)
…yet I got this message when I logged in today:
—————————
Windows Product Activation
—————————
Since Windows was first activated on this computer, the hardware on the computer has changed significantly. Due to these changes, Windows must be reactivated within 3 days.
Do you want to reactivate Windows now?—————————
Yes No
—————————
Very strange. Any ideas?
(Tip: you can capture the text of many Windows dialogs into the clipboard by pressing Control-C while viewing them. The above example came that way. Couldn’t use printscreen while logging in, tho, or I’d’ve shown the dialog too.)
This is just awesome:
…Okay, so it’s a slightly ugly picture, why is it awesome? Read about it here: http://me.eae.net/archive/2005/12/29/canvas-in-ie/. Basically, Emil Eklund of WebFX extended IE to support Canvas elements, the currently most-buzzed new technology in web browsers.
Awesome-er (to me) is that he accomplished in a couple days with IE‘s DHTML Behaviors, just like my xDOM Suite, or Dean Edwards’ Star-Light do. Just like them, it uses DHTML Behaviors to basically improve (fix, enhance, or extend) IE‘s rendering engine. Developers can apply this extension by copying two files and adding a single line of code to pages which use Canvas.
Easy development, 3rd-party browser extensions, easy deployment ….All good examples of why DHTML Behaviors are totally awesome, and great reasons why other browsers should adopt them…
(via Ajaxian, screenshot borrowed from same.)
Nope, I still haven’t seen it, but I can’t wait.
And now I think I gotta go see it in style, though…
SNL – The Chronic of Narnia Rap
(Dunno what’s with the You Tube videos that keep coming my way, but it’s cool that they encourage hotlinking.)