Have specifed table to have no cell padding, borders, etc., and all cell alignments set to "top" and "left", as I want to be able to align things as finely as possible. Looks OK in DW3, but both Netscape and IE add vertical space between the cells, making my images drop down in the layout. I have tried a separate table within the major one, but results are unpredictable.
What's different? Alignment attributes are specified for each cell. That's what was missing. I've also included blank lines in the cells that didn't have anything in them. Netscape doesn't like to render tables the way you want if there are blank cells.
Dreamweaver is a great tool, but should be no substitute for a working knowledge of HTML. Be sure to take a look at the source that is under the page to see how something is coded. You should be able to get a working knowledge of code that way.
To C&M Web Design - You are so right about knowing the html - I am still in a real learning curve! Thank you very much for your time and help - it is very much appreciated, and you have given that ol' learning curve a good boost!
To Christian - It sure is a small world - I used to live next to Rocky Neck too! - I agree, it is a great photo!
Thanks for your response - I was finally, after many experiments, able to get rid of the autoinsertion of lines by specifying the length and width for each cell in the table along with the alignment for each cell in the table - but what a lot of work! You can bet I am going to try your suggestion!
Of course the ""'s are required for Navigator 5.0 and any document that hopes to use XML in IE 5+.
If you truly want to build cross browser code you need to follow the HTML 3.2 and 4.0 standards plus any requirements for XML like the ""'s and case-matching (i.e. <p> cannot be closed by </P> in an XML document). Hopefully we won't have to have do cross-browser code for too much longer (My personal guess is 2-4 years).
The plot thickens! At this point I am wondering what the impact of 2-4 more years of cross-browser code in connection with XML is going to have on those of us using web authoring packages - seems unless updates get offered periodically (as opposed to upgrades) things could get...complicated! And will new browser versions opt to recognize older code as well as newer?
At the beginning of this thread, the statement was made that there is no substitute for knowing how to code manually - I totally agree (working on it!) but also believe that the authoring packages are not going away.
Many thanks for your information - follow it up I certainly will!