IWeb Coding Error?

Question

I have recently created several web pages using iWeb '08 and published on a third-party hosting site (not .mac). A few people who have looked at the sites tell me there is a problem, many cannot see the navigation bar. I have read the forums and there are a number of useful suggestions that address this problem, which is usually due to the users system settings.
However, in asking people whose business is creating websites, I learned about a site to validate xhtml code (http://validator.w3.org/). I used the site and found that about half of my pages are fine, but the other half have an identical error. Here is a transcription of the error:
Line 143, Column 201: there is no attribute "allowTransparency".
…0" marginwidth="0" allowTransparency="true"></iframe>
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Again, this appears on about half of my pages. This sounds like a problem in iWeb creating the code. Has anyone encountered similar problems or can someone offer a fix?
Thanks,
Brad

Answer 1

does it solve the problem?
I think the problems you have mentioned are unfortunately often caused by the different ways different browsers can display the same code. Zero validator errors would not likely make a difference, and some obsolete browsers like IE5 may never work properly.
Regarding navigation menus, if it is a serious problem for your viewers, you probably need to turn off iWeb's navbar and make your own using simple hyperlinks.
Regarding fonts, if viewers' machines don't accurate show what you intended, you may need to turn your text into graphics by adding an invisible amount of shadow.
Regarding layout differences, it's hard to provide any general advice.
In the end, if accommodating a wide range of browsers is essential, iWeb may not be the best app for the job (and no major changes in the way it works are likely for a couple years). I don't know how much better the various alternatives are, but pros normally use Dreamweaver I think.