I'm stumped. I'm not so sure what is the answer to your question. I'll do some research and get back to you if I discover an useful answer. You should email the people at iPage as they probably could answer your iPage question..
Actually, I don't agree with this. While a validater is going to return that you have tags that do not suit some browsers, at least you have tags that work. Not all browsers support CSS in setting body margin attributes, at least they way you have it, you have cross browser compatibility...
Well if he is trying to validate as.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">.
It wont. If he wants it to validate then he would need to put it in a CSS tag or in a seperate style sheet..
Sorry Bonkon, these crappy monitors at work..
I thought the transitional standard let you use the tags that css caused to be deprecated in the strict standard...
That is true with some tags, but there are still tags that it wont allow in certain places for some reason!..
So basically, if you want to validate as bla bla ...html4.0 , you have to use css which is not cross browser compatible and does not allow your iPage site to be viewable the same way in all browsers. Sorry creative, while I'm sure you're right, I would rather code to allow all my visitors to view my iPage site the way it is intended to be viewed. The validater sounds like something composed by Micro$oft to make everyone switch to IE and to hell with the rest...
Yeah I do understansd what your saying about the cross browser issue..
Its what is set out by the W3C guys (who also made the validator), are trying to promote standards, it's the browsers which are not compatable with valid HTML, CSS and even XHTML to a degree..
Who's moto is.
The Web Standards Project: Fighting for Standards in our Browsers.
Are a good group of people who's main goal is to have all browsers recognise all tags in all mark -up languages exactly the same... they have a tough job ahead of them though!!..
Thanks for the help. I have the problem fixed. Re arranged the tables and all is well. All my code works in ns4.75 forward, opera and ie. I don't have issues, generally, getting the code and browsers to play nice. Thanks again. Oh yeah...I am a "she"..
Please use the validator, if only to check:.
* the document structure.
* highlight tags with typos like <IMMG=..> <TBALE>.
* or like <H1 or even ...htm"/A>.
* check the correct nesting of tags.
* check for tags that have the closing tag missing.
And a load of other problems..
My two posts in the very long thread at:.
Have yet more reasons..
If you are happy to leave a few non-standard tags in your code then that isn't usually a major problem. The validator can at least help you clear up other errors that can occur in code...
What would probably be more relevant than an arbitrary "webstandards" validator would be a "browser" validator which informed you which things would not look good in the various browsers. Obviously such an validator is a bit more complicated to construct as it would require you to find,document and analyse the bugs in the various browsers rather than a few simple rules...
My personal opinion is: if a layout solution breaks in various browsers even it if is 'standard' then it is not worth pursuing..
Layout solutions which works in these browsers (even if it is not 'standard') you should use it (provided no standard solution is available which does work in general)..
Standards are fine, but if you write webpages for 'the general masses' where you can not control which browser versions are being used then your number one objective is to ensure a pleasant browsing experience. Standards must then take second place. If common browsers do not support standards then why should it be heralded as the only true solution ? .
I would say this however:.
If css is used for a layout solution which is standards and supported by majority of browsers, but fail in netscape 4.x then I am willing to accept this providing the layout in netscape is still legible. e.g. if the code/layout 'breaks' to the point of not working then I would seek alternate solution. If it is a matter of a border being added or not then for netscape 4.0 I am willing to sacrifize some content as long as it works in Netscape 6/7, MSIE 4/5/6, etc..
Being in business you need to reach all that you can. Not everyone gets sucked into buying the latest, greatest, full of security hole software out there. Most veteran IT people research and know all the junk that really goes on with most software and generally have a say so in companies as to what OS they run, etc which usually means they are not running the latest or they have seen the light and moved to the penguin! JMHO. Anyway I haven't seen a page that I have made that won't work in the browsers I mentioned. WYSISYG isn't always the way to go...