This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
When the page is validated by URL (or the whole page copy & pasted into the "Direct Input" field), the validator sees the page as a browser sees it, processing any SSI, and other preprocessing done by the server, however, when the page is uploaded as a file, some "Errors" are not really errors, but simply incomplete code. I as a somewhat knowledgeable programmer, take these "Errors" into consideration, by ignoring them and concentrating on the actual errors, until the page can be uploaded to a legitimate site, instead of the Apache Server running on my laptop, while I am programming the page. A less experienced programmer might get confused, unless pre-warned.
Hi Rick, (In reply to comment #0) > When the page is validated by URL (or the whole page copy & pasted into the > "Direct Input" field), the validator sees the page as a browser sees it, > processing any SSI, and other preprocessing done by the server The validator does not do any kind of processing. All SSI is always done on the server side (hence the name). > however, when > the page is uploaded as a file, some "Errors" are not really errors, but simply > incomplete code. Yes, if you send content to the validator which is not actually HTML, such as php code or shtml without the SSIs processed, it won't be HTML and thus it will cause errors. > A less experienced programmer might get confused, unless pre-warned. This is possible. Would you have any suggestion as to what warning or information the validator should give?
closing, feel free to make suggestions for error messages in further comments.