The HTML Validator has me Removing...
Hi everyone,
I'm building my pages in Coffee Cup and when I Ctrl+D them, the validator has me removing </p> tags all over the place. Is that right? I know there's probably a "Common Sense" override to the Validator but I don't know if it's wrong or I am.
My page displays properly but I was just thinking that I'm now missing some </p>'s although maybe not?
I provided a "masked URL" to my page below and If someone could so kindly take a quick look at the source code of this, I'd be most appreciative and I thank you all in advance.
Does it look to YOU like I have a bunch of missing </p>'s??
http://goo.gl/v6PXz
I'm building my pages in Coffee Cup and when I Ctrl+D them, the validator has me removing </p> tags all over the place. Is that right? I know there's probably a "Common Sense" override to the Validator but I don't know if it's wrong or I am.
My page displays properly but I was just thinking that I'm now missing some </p>'s although maybe not?
I provided a "masked URL" to my page below and If someone could so kindly take a quick look at the source code of this, I'd be most appreciative and I thank you all in advance.
Does it look to YOU like I have a bunch of missing </p>'s??
http://goo.gl/v6PXz
You definitely have a bunch missing, I would suggest starting from the top and doing a thorough search through your code one by one and fix all the pairs. My guess is that you have a rogue </p> tag somewhere that the validator is seeing and that one is messing up the rest. Find that rogue tag and you should probably be fine. Go back through and fix all your pairs though.
Hi Jo Ann,
Thanks for such a quick reply.
What I've found odd is that on a subsequent Validation (after removing so many </p>'s) that the Validator hasn't detected missing </p>'s
Also, the page displays properly (or it appears to to me).
I'm trying to decide if it's better to have 30 W3C Validator errors or 3.
With the closing </p>'s on some pages I have like 30 errors but with them removed I have either NO errors or very few.
What's your thoughts on this when I've been experiencing this on multiple pages??
Thanks again
Thanks for such a quick reply.
What I've found odd is that on a subsequent Validation (after removing so many </p>'s) that the Validator hasn't detected missing </p>'s
Also, the page displays properly (or it appears to to me).
I'm trying to decide if it's better to have 30 W3C Validator errors or 3.
With the closing </p>'s on some pages I have like 30 errors but with them removed I have either NO errors or very few.
What's your thoughts on this when I've been experiencing this on multiple pages??
Thanks again
Did not see any flags from validator for the ending "p" tags being present. You are using an HTML 4.01 Transitional which allows no closing "p" tags I believe, but I recommend using them all the time. BTW, the font tags are deprecated.
You do have 19 errors and 10 warnings. Just 1 CSS error.
You do have 19 errors and 10 warnings. Just 1 CSS error.
Ron
Hi Ron,
Here's something I've noticed...
Using Ctrl+D or going directly to: http://validator.w3.org/ will both yield different results.
Could you emphasize what you were talking about with the font tags??
Thanks
Here's something I've noticed...
Using Ctrl+D or going directly to: http://validator.w3.org/ will both yield different results.
Could you emphasize what you were talking about with the font tags??
Thanks
<font color="#fff">|</font>
This should all be done in the CSS file not inline in the html anymore.
This line below also has too many <li></li> tags in it, remove the ones highligted:
<li><a href="http://www.your-adrenaline-fix.com" class="home-link">Home<li><font color="#fff">|</font></li></a></li>
This should all be done in the CSS file not inline in the html anymore.
This line below also has too many <li></li> tags in it, remove the ones highligted:
<li><a href="http://www.your-adrenaline-fix.com" class="home-link">Home<li><font color="#fff">|</font></li></a></li>
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.