if you want something done right… DIY.

meanderings of a computer scientist on the brink of sheer insanity.

dear microsoft,

in response to this update about the ‘css improvements’ in IE8, and my previous post about your brilliant ‘version targeting’ concept, i have the following recommendation:
GIVE UP.
what a sordid history “your” browser has endured!it is time you sent it off on an ice floe.

here’s an interesting javascript ‘gotcha’… this block of code:
var y = 37;
var x = parseInt(y,10);
var s = “37″;
alert(x === s);
gives you a “false” alert box, whereas this:
var y = 37;
var x = “” + parseInt(y,10);
var s = “37″;
alert(x === s);
yields “true.”
apparently, ‘x’ is not able to be compared to other strings until it is concatenated […]

recently, i could not for the life of me determine why two strings that should have compared as being equal simply refused to do so… that is, until i set up an alert box to display the underlying comparison character-by-character.
you’ll get different output from this script depending on whether you are viewing it from […]

depending on how precious your time is, you might want to skip to the follow-up.

1. the <select> onchange handler is a kludge, at best
reference: msdn forums
it should be noted that this also an issue within firefox, so do not think that you are made clandestine by your choice of browser alone.
here’s a fun experiment […]