Morton Fox (mortonfox) wrote,
Morton Fox
mortonfox

The look back meme

Borrowed from rockopup:

If you've had LJ for over a year, look back to one year ago today and link back to and quote from your entries of that day.

If you have more than one year, go back for the same day for each past year and quote for them as well.

If you've had LJ for under a year, quote from the first month you had LJ and then halfway through the time you've had it.


One year ago, I was starting to use CSS and hitting some CSS implementation problems in IE. And Mozilla FireFox was still Phoenix back then.


Thursday, February 27th, 2003

12:43a - Deep into browser heck

.
.
.
While browsing some websites on CSS and experimenting a bit, I found that the IE6 auto margin problem went away once I set the correct DOCTYPE. Apparently, IE now has two rendering modes. Depending on what it sees or doesn't see as the DOCTYPE, it will either render the CSS the old broken way or as correctly as it can. This is pretty bizarre stuff but I suppose it makes sense. Websites that rely on buggy IE behavior can continue to rely on buggy IE behavior well into the future, while websites written to W3C standards can set the DOCTYPE and work fine with newer versions of IE. However, I think keeping the broken handling of auto margins is a bit much. Is there any website out there that depends on IE ignoring margin: 0 auto;?

After dealing with that, I hit another IE problem, this time with absolute positioning. This one didn't go away when I added the DOCTYPE so I assume Microsoft is still working on it somehow? I used the workaround described here and now everything looks more or less the same in Phoenix and IE6, and passes the W3C CSS Validator. And so I'm happy, at least until the next CSS rendering problem. Weren't we supposed to leave the bad old days of continual tweaking and working around behind when we moved to CSS? I guess it wouldn't be any fun otherwise. :)

I also updated to the 2/24/2003 nightly build of Phoenix. The new Options dialog looks pretty slick but they seem to have broken the New Tab command. You win some, you lose some.

10:21p - Proxomitron and DOCTYPE?

.
.
.
Proxomitron is a pretty nifty web filter. It is set up as a web proxy between your web browser and the web, and does all kinds of useful things to the http data. Among other things, it kills popup windows, removes ad banners, removes blinking text, removes cookies, inserts userid/password information, blocks images from sites you choose, stops auto-refresh, and so on.

For some of those tricks though, Proxomitron injects Javascript code into the HTML. The problem is it inserts the code before the DOCTYPE. In order for IE to recognize the DOCTYPE, that declaration has to be the first line in the HTML so Proxomitron effectively invalidates the DOCTYPE!
.
.
.
Subscribe
  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 0 comments