IE annoyed me today... again.
Posted by Jesse Rodgers on March 22, 2005 at 03:59 PM
Just posting some bugs I came up against today while working on the new home page… on this lovely spring day.
Negative Margins
I am putting together content for the home page draft, I put in a h1 but the first h1 is really off. All others are OK though. I do some digging, check the code, stick borders around stuff and notice an oditty. So I bug a certain Ottawa Alumni and then we sort of narrow it down to h1 and h2. Then I get pointed to the negative margins bug. Seems the #primarycontent h1 and #primarycontent h2 have a negative margin value in UWblank.css.
This will cause you problems. Not sure the fix other than getting rid of the negative margin value in UWblank.css. It is still there on the production version.. my development version doesn’t have it anymore. You could try resetting the #primarycontent h1 and h2 in your custom CSS. Sorry to inflict a bug fix upon the masses ;)
Whitespace in the code and in the browser
I hate this one, I mean hatewhitespace on lists in IE… oh my goodness. – the options are in the comments of that post. I went with: * html ul li a {height:1em;} in my custom CSS file and all is well.
PHP includes, relative links, and DW templates
This one required a URL be created. What I have done is broken the template for the homepage into serveral includes for the header, footer, and right nav. This is great, DW will manage my relative links to the PHP includes as long as they aren’t in the ‘Templates’ directory. Which is a huge annoyance – when including PHP in your template make sure the extension is .dwt.php and the stuff you include is not in your ‘Templates’ directory.
But what also happens is the relative links inside an included chunk of html does not get managed. No biggie, I can ../../ the link and all should be good. Well no cause that puts it back to the root of the site or development box (pole). So I got IST to create a URL and everything works. When in production that include will have a proper full URL referencing stuff but for testing I just needed it to work. Grr.
Next post: devising a site plan with the new CLF ;)