View Full Version : ffx/ie goof and a question

12-30-2007, 12:20 PM
I got it looking exactly the way I want.

www.chipper.com (http://www.chipperi.com)

Problem 1:

I use Firefox and it look good, but I took a look in IE to make sure all was good. In IE it puts a grey separator between all of the buttons on my navbar, Not a big deal I can live with it if I have to.

Problem 2:

I intend to add more buttons to my navbar as I add info to the site. Which is the main reason I decided to learn CSS. Is there anyway to put html in my external css so I wont have to go to every html doc on my site and add the line

<li><a href="whatever.htm" title="whatever">Whatever</a></li>

My ultimate goal is to have 1 master css template that all I have to do is add the center text to. As well if I want to make an ad or navbar change I can do do it from the CSS and update every page on the site.

Did that make sence...I hope so.

And lastly problem3:

Why can I not indent my text? It is pressed right up gainst the edges of the field. (fixed)

12-30-2007, 03:40 PM

Put this code at the top of your file:
* { margin: 0; padding: 0; } It generally resolves issues like that.
Your best bet is PHP. Give all your pages with the .php extension, instead of .htm or .html. Take out your nav. bar and put it in a file named navbar.php. Then, where you want the bar, insert this bit of PHP code
<?php include("navbar.php"); ?>

12-30-2007, 04:55 PM
The 'included' file will be parsed as html by default, so the included file could remain as an html file.

<?php include("navbar.html"); ?>
If it contains no php code, it will run quicker if you declare it as html, too.
Of course, the calling page would need to be a php file extension, unless you alter your .htaccess file to send all html through the php parser. Easy enough to do, but it also slows down the pages a bit.

Also, your page is set to run in Quirks Mode.
THere is a Sticky about Which Doctype to use on a page. I suggest you have a read and change your Doctype to suit your coding.
And run it through the w3c validator. A few things to change.

Image tags should be closed with a slash <img ... />
and the ampersands in the links should be html entities "&amp;" to cure a few things.

Not much you can do about the Warnings from the Ad scripts... :(

12-30-2007, 05:12 PM
A very minute time. I say PHP because your navigation bar is one of the most likely candidates for treatment by a server-side language.

Seeing as he's triggering use of an SGML parser, he doesn't need to use empty element closing tags?