validation w3.org (Full Version)

All Forums >> [Web Development] >> General Web Development



Message

wonway -> validation w3.org (2/9/2007 12:18:17)

I searched and read a lot in the form. However I could not find my problem.
Using FP2003, when I validate the HTML I see corrections needed but when I check script the correction is there. also, corrections are listed for Lines and Columns that are not in my script. Example Line 409 when my last line is 312. It wants me to take out the (space) between "Microsoft Border" if I do I lose my borders it said the same thing about "MicrosoftTheme" which I did but noticed no change.



Tailslide -> RE: validation w3.org (2/9/2007 12:26:03)

It's difficult to tell without seeing your site - but I'd say that it's because you're using some sort of microsoft theme which is unlikely ever to validate. Your choices are to either dump the theme and get the validation or to keep the theme and put up with the ugly invalid code. If you're not too happy about dumping the theme then it'd be wise just to check that the site looks ok on other browsers (M$ stuff quite often only looks any good on M$ browsers).

The validator is reading the actual lines that appear on the published page whereas locally, when you look at it, you're not seeing all the extra stuff that gets added by includes or themes or whatever.



wonway -> RE: validation w3.org (2/9/2007 13:07:56)

http://www.classictruckconsoles.com/



Tailslide -> RE: validation w3.org (2/9/2007 13:38:45)

There's a mixture of errors there - some of which you can fix (missing alt attributes for instance) some of which you can't fix unless you dump the theme (the theme using two words for it's name for instance - "microsoft border" - when it should only be one).

I don't know offhand which bits M$ puts in and is therefore out of your reach to fix though.

Validation is a "good thing" but that said - sometimes you might have to just live with an error. You need to look at what you can fix and what you can't. Alt attributes for images are important and should be fixed. Whether having a two word name will actually cause an issue in a browser or not... dunno. Quite possibly not - at least not yet. Having a set height on a table might not be a great idea as when people make the text bigger in their browsers - it might break the layout. You need to experiment with it and make sure that it doesn't.



Kitka -> RE: validation w3.org (2/9/2007 15:10:25)

quote:

... corrections are listed for Lines and Columns that are not in my script. Example Line 409 when my last line is 312.


To see the code as the validator is seeing it, check the box near the top of the Validator page that is labelled "Show Source", then click the Revalidate button.

That will include all the source code as the validator sees it (with line numbers) below the errors, so should make it easier to find the lines that need correcting on your local copy.



Kitka -> RE: validation w3.org (2/9/2007 15:18:11)

quote:

... some of which you can't fix unless you dump the theme (the theme using two words for it's name for instance - "microsoft border" - when it should only be one).


Tailslide: Microsoft Shared Borders are not a part of themes. They are a crude proprietry form of includes, and can be used with or without a theme.

wonway: You can safely ignore the validation error for the "Microsoft Border" and your shared borders will still work in all browsers. It just means you won't be able to claim full validation for the page once you have eliminated all the other errors.



Tailslide -> RE: validation w3.org (2/9/2007 17:09:40)


quote:

ORIGINAL: Kitka
Tailslide: Microsoft Shared Borders are not a part of themes. They are a crude proprietry form of includes, and can be used with or without a theme.


Thanks Kitka - I make it a point not to become too familiar with the horror that is M$ WYSIWYGs (just in case any of it rubs off)!!



wonway -> RE: validation w3.org (2/10/2007 6:48:07)

Thanks all, I checked Alt attributes, I have checked all my tables and I do not include height. Also, the other problem I mentioned is in Validation, it shows errors but in my script the errors are not there, it also shows more lines than FP shows.
Here is FP's Line 61: </table>, and here is Validation error for Line 61: Error Line 61, column 146: there is no attribute "BORDERCOLOR" .

...px; padding-bottom: 1px" bordercolor="#FFFFFF">

In reviewing the Source Listing it is not in the same order it lists the borders first than it starts with the rest of the page. Am I missing something in FP to show coding in the order as Validation.



jaybee -> RE: validation w3.org (2/10/2007 7:33:59)

If you check the line numbers in FP they won't match. FP adds in extra code when the page loads.

To see the line numbers the validator is talking about you need to View Source in the browser which gives you the full rendering of the page.

I find Firefox is a better browser for this as it has a "Go to line number" option when you have the page source open. On your main page, line 61 shows as 
		<td vAlign="top" width="91%" bgColor="#C0C0C0" style="padding-left: 4px; padding-right: 4px; padding-top: 1px; padding-bottom: 1px" bordercolor="#FFFFFF">



wonway -> RE: validation w3.org (2/11/2007 6:28:55)

If FP does not show the same Line # than how do I find the Line to correct. I viewed Source and checked it against Validation. Take Line 61, validation shows " missing and Source shows " there. This is consistent throughout validation. Do I just have to live with this maybe its norm for FP. Anyway sure would like to find how to locate and make the corrections.



womble -> RE: validation w3.org (2/11/2007 11:31:30)

If you use Firefox, you can use the "Find" feature (on the edit menu) to go to that line - Use 'view source' (either from the 'view' menu, or from the web developer toolbar) in the browser to get the page source up, and then copy and paste part of that line into the 'find' box that appears at the bottom of the screen, and FF will highlight the line for you.



wonway -> RE: validation w3.org (2/12/2007 10:29:27)

Either I am missing something or I am the dumbest mouse on the pad.

I can view source and see the line but there is NO error shown but validation says error. So what's to fix and if I did find an error to fix how can I find it if FP does not show the same Line.

Did some searching for Border Code and found post by Kitka. So now I found the code but I do not show errors that validation does. I even created an Error and revalidated and it showed my code with the error but did not say it was an error.



TravelswCharlie -> RE: validation w3.org (2/12/2007 21:48:12)

I'm about where you are, Wonway, so I can't give you any real help, but I can tell you what has helped me.

I've found another validator that makes it a lot easier to find what needs to be fixed.

It's called "Total Validator". It does the same W3C validation, but adds line numbers and identifying "error codes", along with a lot of explanation that makes it easier to find the errors.

http://www.totalvalidator.com/

Pasted from the program:

"Total Validator is a free one-stop validator or all-in-one validator comprising a HTML validator, an accessibility validator, a spelling validator, a broken links validator, and the ability to take screenshots with different browsers to see what your web pages really look like. Currently Total Validator provides the following main features:

* A tag validator that validates the basic construction of your pages
* True HTML validation against the W3C Markup Specifications or ISO/IEC definition using the published DTDs (2.0, 3.2, 4.0, 4.01, ISO/IEC, XHTML 1.0 and 1.1)
* An accessibility validator that validates against the W3C WAI Accessibility Guidelines and US Section 508 Standard
* A broken links validator that checks each page for broken links
* A spelling validator that spell checks the content of your pages (English, French, Italian, Spanish)
* Snapshots (screenshots) of your pages in different browsers, on different platforms, at different resolutions
* A desktop tool so you can validate pages before you publish, and pages behind firewalls
* A Firefox extension for fast, one click validation





wonway -> RE: validation w3.org (2/13/2007 11:22:33)

thx everyone for your help. I'll keep learning and appreciate the forum.



jaybee -> RE: validation w3.org (2/13/2007 11:48:47)

Ahhhhh I've just twigged, are you looking for this in design mode?

OK, I load up your main page and run it through the validator and lets take one example. 

Error  Line 61 column 146: there is no attribute "BORDERCOLOR".

...px; padding-bottom: 1px" bordercolor="#FFFFFF">


I go to view source and look for line 61 and it's 

		<td vAlign="top" width="91%" bgColor="#C0C0C0" style="padding-left: 4px; padding-right: 4px; padding-top: 1px; padding-bottom: 1px" bordercolor="#FFFFFF">


So now you go to FrontPage. Open that page then click on the CODE tab at the bottom, there you'll see all of your code. Then you need to look down it until you find that line or
Edit>Find and then paste that line in.



wonway -> RE: validation w3.org (2/13/2007 12:11:08)

I've been in Code all along. The line 61 that we have been referring to in in my Border file, left.htm and the code is the same as you listed and it is correct there is no error.



Kitka -> RE: validation w3.org (2/13/2007 17:34:49)

quote:

the code is the same as you listed and it is correct there is no error.


There is an error. "Bordercolor" is Microsoft proprietary code, and is not interpreted by Mozilla browsers (including Firefox) or Opera.

To make that bit of code valid you need to replace this: 
bordercolor="#FFFFFF"


with this: 
style="border-color:#ffffff;"


Then, not only will it be valid code, but your border will be rendered correctly in all browsers.



wonway -> RE: validation w3.org (2/14/2007 12:00:34)

All right Kitka, tomorrows work. Taking back my site one bite at a time.



TravelswCharlie -> RE: validation w3.org (2/14/2007 14:19:17)


quote:

ORIGINAL: Kitka

There is an error. "Bordercolor" is Microsoft proprietary code, and is not interpreted by Mozilla browsers (including Firefox) or Opera.

To make that bit of code valid you need to replace this: 
bordercolor="#FFFFFF"


with this: 
style="border-color:#ffffff;"


Then, not only will it be valid code, but your border will be rendered correctly in all browsers.


I have the same type errors... code that is correct in FrontPage but will not validate, so many corrections such as you describe need to be made.

Others refer to "background", "margin", and even "font".

My question is... is there an "invalid" to "valid" cross-reference list published somewhere that will help in making these corrections?

Thanks,



wonway -> RE: validation w3.org (2/15/2007 11:38:52)

that change is not my problem I tried it and nothing changed.
nothing seems to work.
Validation says I am missing:
attribute "ALT" (>) not specified
no attribute "BORDERCOLOR (")

this is happening through out validation it doesn't seem to see all of these: (",>) even though they are in the code.



TravelswCharlie -> RE: validation w3.org (2/15/2007 15:46:46)


quote:

ORIGINAL: wonway

that change is not my problem I tried it and nothing changed.
nothing seems to work.
Validation says I am missing:
attribute "ALT" (>) not specified
no attribute "BORDERCOLOR (")

this is happening through out validation it doesn't seem to see all of these: (",>) even though they are in the code.


Well, I'm not following much of what you say there, but to tackle one thing at a time, look at this:

Right click on your sunset photo then select "Properties". That displays a box titled "Element Properties".

The last item in the box, "Alternate Text" reads "Missing".

Now look at my website, www.campingandrving.com, and do the same thing.

Right click on the large photo of an RV (behind a sign with a rabbit that says "kick back"), then select "Properties" to pop up "Element Properties".

The last item in the box, "Alternate Text" reads "Charlie the RV".

Perhaps you are just putting your code in the wrong place?




.



wonway -> RE: validation w3.org (2/16/2007 9:13:54)

charlie, I did the change, don't know how I missed it went ahead and checked all my other images and they were ok. But knowing me I probably missed something.

I was able to remove 3 errors. But I am still stuck on the others missing <,>," that are not missing in my code.

3 down 14 to go, Guess I will have to live with the (space) in Microsoft Borders and Theme.

Thx everyone



jaybee -> RE: validation w3.org (2/16/2007 9:53:20)

quote:

code that is correct in FrontPage but will not validate
FrontPage code is not valid. It contains a lot of Microsoft's own code that is not valid HTML.

The errors that are produced by the validator can be checked for the correct method in www.w3schools.com

Here are some articles:

http://www.webaim.org/techniques/frontpage/
http://msdn2.microsoft.com/en-us/library/aa218654(office.11).aspx

Here are some code cleaners.

I've never used this but the guy uses FP himself.

Integrate HTML Tidy



wonway -> RE: validation w3.org (2/16/2007 10:34:49)

I used FP code cleaner and eliminated 1 error. It also removed MS Borders and Theme and replaced code. Thx again.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.1875