soledad penadés

repeat 4[fd 100 rt 90]

Found this comment in a weblog:

i was minding my own business one day then suddenly this thing popped up asking me to debug using microsoft script editor. what is debug? why is it happening? when i press ok, it stopped and said that something is null and not an object. leaving me no choice but to press break. what is break? but it is just hanging there and i can't use my program. and i don' t understand what the whole thing is about. please help….

(from MSE at Erik's weblog)

Unfortunately I couldn't feel more identified with it. It might be surprising but when you're working with computers during 8+ hours a day the last thing you want to get is an error like that one. Even if you know what's going on, what's debug and what's break. It isn't your business, and it shouldn't be, but it prevents you from doing yours.

It's like a plumber being greeted with an stack overflow when he comes back home after a long plumbing and unblocking day.

Ahhh computers! Diabolic weapons!

… bugs like this one do you need to switch to Firefox, Safari, Opera or Camino?

Once again Internet Explorer proves to be extremely dangerous, allowing people to execute programs in your pc - without your previous approval, of course. And seems like the fixes microsoft makes are breaking sites which worked properly before.

C'mon. I know you can do it. Seriously.

Kill Bill's Browser!

At last someone decided to speak serious, honestly!

If you don't kill Bill's browser, someone will kill you! (and I presume there's a vast amount of people willing to do so, namely web developers).

Make the switch today, they say.

… to face all the replies and comments from readers of Internet Explorer and MSN Search blogs.

First time I saw the Internet Explorer blog, it had a long list of comments from Very Angry People complaining about past  (and future!) Internet Explorer versions, lack of standards support and so, so on…

Although I share most of the opinions of those furiosus posters, I should say that I don't agree on the way they expressed their ideas. Entering into an already started project, taking code from others… is always hard… and you'll be the new responsible for errors that are inherited from previous versions… And well, that's their job, but it doesn't mean they have to suffer unpolite and agressive users and that lack of trust in their capability to amend past errors.

Yes, I do know how microsoft is. But I'm very positive today… ;)

I was using jscalendar in a form. The form is inside a div which is inside another div, etc. Each div had modifiers for position. It was showing nicely on ie, ie mac and firefox, everything as expected.
But when adding the calendar the party started! IE decided to move the calendar to the right. Hum… always on the same position… then after the weekend I have had the magic idea: it was not calculating the final position after all the nested divs. Current position was the one without the margin of the new div. So I assigned position:static to the container div and whops! now the calendar div appears in the right size.
Those oddities in a deadline-stressed mode are nightmares!