Browser Compliance »
For those of you who have been trying to read my site in a Mozilla-based browser, you'll be happy to know that I'll probably be keeping up on the compliance now that I'm using one on a regular basis.
The first problem I ran into? Seems the sidebar had dropped below the entries. I'm not really sure when it happened, I only noticed it today. The fix was to add a single line to the CSS:
position:absolute;
Strangely, I didn't actually have to specify an absolute position, yet it worked. I've removed the addition and it goes back to the funkiness displayed earlier. I'm not going to worry about it. At least it works.
The second problem was a little more challenging. The new redirect function in Movable Type version 2.66 has some invalid XHTML code in it. The fix? Either modify Comments.pm to change the code, or upgrade to version 2.661. Guess which I chose? That's right. I mucked with it myself. Then I noticed version 2.661 actually fixed this for me, and I upgraded too. Take this as a warning - you may not always want to follow my lead on things.
Comments (3)
hmmm.....thanks for fixing it once, but I'm using Mozilla Firefox 0.8 and it seems to be doing exactly what it was doing before :-(
Posted by Jon Mark Allen | March 2, 2004 4:55 PM
Everyone knocks old IE but I am yet to see a browser that consistently renders pages as well as IE does. Even when it comes across an error in markup it still fails-safe.
Posted by Stephen | April 17, 2004 9:53 AM
everyone knocks PIGLATIN but people will continue to understand what I'm saying ... since -I- use ONLY PIGLATIN, and if you dont you should ...
well yeah, if you're using your OWN (read: M$) version of HTML-parsing!! WHY do so many people think M$ is the be-all, end-all, when they do so many things wrong, rather than according to WWW standards!
thanks
Posted by Bob Lueredos | May 26, 2004 3:31 PM