Web 2.0 — opening up a whole new world of Internet Explorer quirks!

Just when I needed it least, Internet Explorer has thrown me another curveball.

I’m hard at work trying to seem like less of a 20th Century web dinosaur by acquiring new skills with these techniques that are loosely lumped together into what some call “Web 2.0.” Key among these is an approach called AJAX (Asynchronous JavaScript and XML). Fun stuff. I’ve been working for the past several days on an interactive registration form for a site at work, using AJAX. Of course, as usual, I’m plugging away in Safari and Firefox, but eventually I decided to check out how things are looking in Internet Explorer.

[When I figure out an emoticon that represents my head exploding, I’ll insert it here.]

IE is consistently barfing on what it claims is a syntax error that I eventually tracked down to the evalScripts function in prototype.js. Well, at least it’s not my own code that’s making it crap out this time. Or is it? With IE you never can tell. Maybe evalScripts is buggy (even though I can find no evidence to that effect) or maybe it’s just the code in my script that’s being thrown at it. Whatever the case, once again all forward progress has come to a grinding halt while I scour the Internet fruitlessly for a solution.

Although this turned out not to be a solution to my problem, I just have to refer you to this developer’s blog entry on a typical IE workaround. Yes, I tried this, even though I was almost positive his problem was completely unrelated to my own (which was the case). Nevertheless, when a problem does arise in IE, the most likely eventual result of one or more days’ worth of sleuthing is the resigned acceptance of such hokey code bloat, rather than anything even remotely satisfying (or even logical).

There you have it. As for my own problem using prototype.js with IE, I did find a solution. Yes, it was my code, and it was something I had seen previously that was pretty much staring me in the face, if I had just bothered to heed Thomas Fuchs’s sage advice.

It all comes down to standard practice for wrapping <script> tags in HTML. I still have the habit of doing it this way:

<!–
//–>

The funny thing about that is that I know it’s completely pointless these days. It’s done so that browsers that don’t support JavaScript don’t inadvertently display the JavaScript code in the web page. But every browser has supported JavaScript since about 1997, so it’s pretty ridiculous to keep doing that. Especially given that, the way the sites I’m working on are so utterly dependent upon JavaScript, you’d never even get to the page in question without it.

However, with XMLHttpRequest (which is at the heart of AJAX), and just the increasing complexity of JavaScript in general, it’s become necessary to wrap script code in a new tag to ensure that browsers handle the code properly. To wit:

// <![CDATA[
// ]]>

Just as Thomas Fuchs said. And just as has been lingering in the back of my mind for the past several weeks, since I first discovered his wonderful tool based on prototype.js, Scriptaculous. I’ve learned my lesson.

So what’s going on here, exactly?

Good question. I had redesigned my site, in conjunction with a transition to using the Drupal engine. But then I learned just how much of a sitting target for spammers a Drupal site really is, so that’s out the window.

For now I’ve rolled back to the old site (with the 3 or 4 blog entries I posted in Drupal floating out there in the ether). I’m in the process of moving everything over to a new server anyway, so for now the site will remain in this old look until I get everything on the new server ready to roll out.

How do you place a value on something that’s intrinsically useless?

I’ve always been skeptical of the “value” of jewelry, and in particular of diamonds. Fortunately I found in SLP a companion who doesn’t believe that the magnitude of my affection is commensurate with the size of a rock on her finger.

Today I was exploring some sites for design and layout ideas, and along the way I visited Digg. As it happened, the top link on Digg at that moment was an article from the Atlantic Monthly entitled “Have You Ever Tried to Sell a Diamond?”

Now, it’s well-known that De Beers is far from the most beneficent corporation in the world, and the brutal story of “blood diamonds” has been the topic of hip hop songs and movies alike. But before those atrocities could be committed, someone had to invent a perception of value. Finally in this article I have documented proof (in extensive detail) of what my gut has been telling me for years.

Interestingly enough, and I had not noticed this initially, the article is actually from the February 1982 issue of the magazine. It speaks of several developments in recent years (those years being the late ’70s and early ’80s) that would threaten the De Beers monopoly. Now, I haven’t been a close follower of the diamond industry, but I know De Beers still rules the roost.

Now there’s something I haven’t seen in years!

I was in a neighborhood grocery store today. It’s one of those old grocery stores that used to be considered a “supermarket” back when it was built, probably in the late ’60s, but now seems quaint and almost tiny. It’s been remodeled, probably many times, but in general its decor looks modern but the layout of the store hasn’t changed a bit. Walking into the store is like walking into my childhood.

That fact really hit home today when I noticed, near the checkout, a very old, very faded illuminated sign/clock reading “Thank you for shopping with us.” But the thing that really caught my eye was barely visible — a long forgotten logo decal on the clock face. But even though I could scarcely see it at all, I immediately recognized it as something that has been burned into my mental image bank even though I haven’t seen it in years (if not decades):

Red Owl Logo

That freakin’ owl used to give me nightmares when I was 3!

Recognize it? Don’t recognize it? Here’s more…

This gives “scare quotes” a whole new meaning…

Once SLP and I get a taste for the classic Thanksgiving dinner, we just can’t get enough. We often make a turkey in late October/early November in preparation for Thanksgiving, and often within a day or two of eating the last of the Thanksgiving leftovers, we get another turkey and do it all over again.

Such was the case today. However, even though Thanksgiving was just three days ago, fresh turkeys are already hard to come by. I was at a local Cub Foods today and found several packaged fresh turkey halves, presumably cut up from the large stock of fresh Thanksgiving turkeys that went unsold.

But… when I got home, there was something about the label on the package that really did put the “scare” in “scare quotes“:

“Fresh” Turkey Half

Yikes.