1 bug. 1 silly, complicated bug. and then i think the new site is all but ready.

ive got it 100% on firefox. 98% on safari. and then the ies are giving me trouble. over some silly show/hide-resize nonsense. and ie5 is sucking on some complicated css, but really. i dont think i have much symapthy for you if you are still running ie5.

ill trounce it this weekend. thats the goal. and by monday, with any luck, youll be surprised. and filling my inbox with bug reports. which i wont get to because ill be a working man. like eric.

and eric — my advice to you is dont watch ‘american beauty.’ because the fear you describe is summed up in that movie so perfectly. i bawled for hours after seeing it the first time.

im less scared nowadays. im dating someone much younger than me, i have been in school for a while, im starting a very kiddish job…i no longer fear living in the suburbs. but my day will come, i have no doubt.

no the meantime, i pour over code, wondering why ie seems so incapable of applying a ‘position:absolute’ to a div on the fly.

back to cursing out old crappy browsers. that cant answer.

* * *

an hour later. ive squashed the bugs. most were minor. the ones that werent were tweaks to make ie play nice. though i think in the last hour, ive decided to ax support for ie5. ie5.5 is working fine. but there is 1 javascript error and a significant css bug in ie5. and im not sure i want to spend the time building hacks and workarounds for it.

it sounds lazy, but in reality, i want clean code. i want things correct. and written once. not some branching nightmare to support everything that has ever existed.

at last check, ie5 is about 7% of the browser market. my question is this: do any of you use it? do any of you care if ie5 is supported?

(because to make this work, im going to have to branch the js. which just is…uncool.)

Popularity: 1% [?]