avoid the box model... unless you are experienced with it, getting this to work correctly in both browsers is a nightmare.
set your body text-size to 77%, then any text styles you define use 1.25em (for example)... this usually gets things like text and layout pretty good for me..
dont know what you mean to be honest, I am pretty new at this, so I am learning as I go. I think its something to do with teh float left in the style sheets of the tables.
they are only general comments for getting things to work in those browsers.... a url is still needed if you want anyone here to actually look at what you are talking about
then i just checked for proper nesting (all divs pair up with a closing one...)
Thats it..
sometimes to make best use of float: is to not use it.
(or at least making use of float on one element sometimes means you dont have to use it on another..)
If you cannot make these changes i can email you the local html file for worked on...
no, it is the float:left that is forcing it underneath. The float:left on the sidemenu class should put the menu along side the main panel.
as for the divs, no you didnt, but i did while i was working on it... and then just checked it in a validator which showed up a closing div that didnt have an open.
the code below should work in IE6 (which is what i tested it in).
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<title>Peterlee Fire Company Ltd</title>
<base href="
<div class="mainpanel">
<h1>Extinguishers</h1>
Peterlee Fire Company can supply a full range of stored pressure factory filled extinguishers
to cover all fire types including a selection of specialist models. Each is manufactured
according to British Standards to provide maximum fire fighting capability and is labelled
with the BSI kite mark as well as full detail on the extinguisher type and fire classification
it is suitable to extinguish. <br>
Ok, reverse to begining. First step to proper coding is proper doctype. That will ensure your page will look the same (or at least as close to that as it can) on all browsers. Pick one of these: Valid Doytypes
Come back with the findings after that.
I personally use XHTML 1.0 Strict which is the strictest. The easiest (allows for most freedom with tags) and still acceptable should be HTML4.01 Transitional. It depends on what you are producing. Do you have:
1. All tags and attributes in lower case?
2. All empty tags (like <img>, <br>, <hr>) closed?
3. All styling done with CSS?
If you answered yes on all questions, go with xhtml. If not, go with html4
Vragabond - The doctype that is there is produced by Dreamweaver... full doctype declarations are usually only applied when using a strict doctype.
I also use XHTML strict, but for 4.01 transitional the doctype being abbreviated shouldnt cause a problem...
BTW, when i say usually here, I mean in practise. It is technically correct to have a full doctype according to the w3c.
jez, I know you are trying to help but sometimes it is not good to give advice when you don't know if it holds true or not. Correct (valid and complete) doctype will switch your browser's behaviour from quirks to standards-compliant mode. For FF, there isn't much difference, for Opera there's a huge improvement for the better and for IE there's a considerable improvement. The list I gave in the link features all valid and complete doctypes you can use on the website. If the one used is not on the list, it is considered invalid or incomplete and does absolutely nothing. It does not matter that DreamWeaver applies that -- DW is a WYSIWYG html editor, no more. It is not authority in HTML. The doctype it produces is incomplete and as such completely useless. That said, the valid list of doctypes I provided stands.
I was simply pointing out that there was already a doctype, whether right or wrong which was put there by an editor.
I know how bad the HTML of DW is, my point was that it would be easy to assume that since there was one, that it would be correct especially as an expensive piece of software put it there.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.