Home » RADICORE development » Bug Reports » sample v3.0.0 XHTML markup errors
| sample v3.0.0 XHTML markup errors [message #3294] |
Mon, 07 January 2013 14:23  |
jjtoranzo2004
Messages: 261
Registered: September 2012
|
Senior Member |
|
|
Tony,
I checked one page of the sample application
http:// www.tonymarston.net/sample/person_list.php?session_name=samp le
with the W3C Markup Validation Service (http://validator.w3.org/).
The service found one markup error.
Checked as XHTML 1.0 and XHTML 1.1
==================================
ERROR 1
Error document type does not allow element X here; missing one of Y start-tag
------------------------------------------------------------ ------------------
The mentioned element is not allowed to appear in the context in which you've placed it;
the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned.
This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element
(such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 209, column 68: document type does not allow element "input" here;
missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
<input type="hidden" name="session_name" value="sample" />
Thanks.
|
|
|
|
| Re: sample v3.0.0 XHTML markup errors [message #3304 is a reply to message #3294] |
Thu, 10 January 2013 08:54  |
jjtoranzo2004
Messages: 261
Registered: September 2012
|
Senior Member |
|
|
Tony,
I checked one Add 1 page of the sample application
http://www.tonymarston.net/sample/person_add.php
with the W3C Markup Validation Service (http://validator.w3.org/).
The service found two errors (generated by empty ids (id=""):
syntax of attribute value does not conform to declared value
The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the "selected" attribute must be either minimized as "selected" or spelled out in full as "selected="selected""; the variant "selected=""" is not allowed.
Line 95, column 42: syntax of attribute value does not conform to declared value
Line 140, column 42: syntax of attribute value does not conform to declared value
<option value="" id="" selected="selected"> </option>
<option value="" id="" selected="selected"> </option>
------------------------------------------
but I think the nu validator (http://html5.validator.nu/) puts it better:
Error: Bad value for attribute id on element option: An ID must not be the empty string.
From line 95, column 21; to line 95, column 63
<option value="" id="" selected="selected"> </opt
Syntax of id:
An ID consists of at least one character but must not contain any whitespace.
Error: Duplicate ID .
From line 140, column 21; to line 140, column 63
<option value="" id="" selected="selected"> </opt
Warning: The first occurrence of ID was here.
From line 95, column 21; to line 95, column 63
<option value="" id="" selected="selected"> </opt
Error: Bad value for attribute id on element option: An ID must not be the empty string.
From line 140, column 21; to line 140, column 63
<option value="" id="" selected="selected"> </opt
Syntax of id:
An ID consists of at least one character but must not contain any whitespace.
Thanks.
|
|
|
|
|
|
|
|
| Re: sample v3.0.0 XHTML markup errors [message #3317 is a reply to message #3314] |
Sat, 12 January 2013 13:53 |
jjtoranzo2004
Messages: 261
Registered: September 2012
|
Senior Member |
|
|
Tony,
Thanks for fixing everything.
I checked
http://www.tonymarston.net/sample/help.php?session_name=samp le&taskid=person_list.php
with the W3C Markup Validation Service (http://validator.w3.org/).
Pe
It found the following errors:
-------------------------
Notes and Potential Issues
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Warning Mismatch between Public and System identifiers in the DOCTYPE declaration
This document uses an inconsistent DOCTYPE declaration. The Public Identifier -//W3C//DTD HTML 4.0 Transitional//EN declares the HTML 4.0 Transitional document type, but the associated System Identifier http://www.w3.org/TR/html4/loose.dtd does not match this document type.
The recommended System Identifier for HTML 4.0 Transitional is http://www.w3.org/TR/1998/REC-html40-19980424/loose.dtd.
The safest way to use a correct DOCTYPE declaration is to copy and paste one from the recommended list and avoid editing that part of your markup by hand.
Info No Character encoding declared at document level
No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
See this tutorial on character encoding for techniques and explanations.
↑ Top
Validation Output: 4 Errors
Error Line 2, Column 16: there is no attribute "XML:LANG"
<html xml:lang='' lang=''>
✉
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.
Error Line 2, Column 25: syntax of attribute value does not conform to declared value
<html xml:lang='' lang=''>
✉
The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the "selected" attribute must be either minimized as "selected" or spelled out in full as "selected="selected""; the variant "selected=""" is not allowed.
Warning Line 5, Column 58: NET-enabling start-tag requires SHORTTAG YES
<link rel='stylesheet' type='text/css' href='help.css' />
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.
Error Line 6, Column 7: end tag for element "HEAD" which is not open
</head>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Error Line 7, Column 6: document type does not allow element "BODY" here
<body>
✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Warning Line 11, Column 48: NET-enabling start-tag requires SHORTTAG YES
... list records on the PERSON table.<br /><br />For a description of screens of ...
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.
Warning Line 11, Column 54: NET-enabling start-tag requires SHORTTAG YES
...records on the PERSON table.<br /><br />For a description of screens of type L...
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.
-------------------------
Perhaps you could convert help pages to XTHML.
Thanks.
|
|
|
|
|
|
|
|
| Re: sample v3.0.0 XHTML markup errors [message #3320 is a reply to message #3319] |
Sun, 13 January 2013 08:05 |
jjtoranzo2004
Messages: 261
Registered: September 2012
|
Senior Member |
|
|
Tony,
I checked the calendar of the sample application
http://www.tonymarston.net/php-mysql/calendar.php
with the W3C Markup Validation Service (http://validator.w3.org/).
It found the following errors:
-------------------------------------------------------
Error found while checking this document as HTML 4.01 Transitional!
Result: 1 Error, 6 warning(s)
Notes and Potential Issues
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Warning No Character Encoding Found! Falling back to UTF-8.
None of the standards sources gave any information on the character encoding labeling for this document. Without encoding information it is impossible to reliably validate the document. As a fallback solution, the "UTF-8" encoding was used to read the content and attempt to perform the validation, but this is likely to fail for all non-trivial documents.
Read the FAQ entry on character encoding for more details and pointers on how to fix this problem with your document.
Warning Unable to Determine Parse Mode!
The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
the MIME Media Type (text/html) can be used for XML or SGML document types
No known Document Type could be detected
No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.
Warning No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.
No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.
The document was checked using a default "fallback" Document Type Definition that closely resembles "HTML 4.01 Transitional".
Learn how to add a doctype to your document from our FAQ.
Info No Character encoding declared at document level
No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
See this tutorial on character encoding for techniques and explanations.
Validation Output: 1 Error
Error no document type declaration; implying X
The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.
Line 1, column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
<html>
Warning NET-enabling start-tag requires SHORTTAG YES
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.
This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.
Line 18, column 65: NET-enabling start-tag requires SHORTTAG YES
<p>Enter Year: <input type="text" name="year" size="4" value="" />
Line 19, column 33: NET-enabling start-tag requires SHORTTAG YES
<input type="submit" value="GO" /></p>
-------------------------------------------------------
Line 1, column 110: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
...HTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html>
Line 14, column 12: there is no attribute "align"
<div align="center">
Line 17, column 51: value of attribute "method" cannot be "GET"; must be one of "get", "post"
<form action="/php-mysql/calendar.php" method="GET">
Errors found while checking this document as XHTML 1.0 Strict!
Result: 3 Errors, 3 warning(s)
Validation Output: 3 Errors
Error value of attribute Y cannot be X; must be one of %3
The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the "selected" attribute must be either minimized as "selected" or spelled out in full as "selected="selected""; a value like "selected="true"" is not allowed.
Line 17, column 51: value of attribute "method" cannot be "GET"; must be one of "get", "post"
<form action="/php-mysql/calendar.php" method="GET">
Error Missing xmlns attribute for element X. The value should be: Y
Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
<html xmlns="http://www.w3.org/1999/xhtml">
Line 1, column 110: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
...HTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html>
Error there is no attribute X
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.
Line 14, column 12: there is no attribute "align"
<div align="center">
-------------------------------------------------------
Error HTML5 Validator Error
Line 14, column 20: The align attribute on the div element is obsolete. Use CSS instead.
<div align="center">
-------------------------------------------------------
Perhaps you can convert the page to XHTML 1.0 Strict.
Thanks.
|
|
|
|
|
|
|
|
|
|
| Re: sample v3.0.0 XHTML markup errors [message #3324 is a reply to message #3323] |
Sun, 13 January 2013 15:50 |
jjtoranzo2004
Messages: 261
Registered: September 2012
|
Senior Member |
|
|
Tony,
Both
http://www.tonymarston.net/php-mysql/amortise.php
http://www.tonymarston.net/php-mysql/converter.php
are missing a line like
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" >
(See http://www.w3.org/International/O-charset)
The W3C Markup Validation Service (http://validator.w3.org/) found the following:
----------------------------
Notes and Potential Issues
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Warning No Character Encoding Found! Falling back to UTF-8.
None of the standards sources gave any information on the character encoding labeling for this document. Without encoding information it is impossible to reliably validate the document. As a fallback solution, the "UTF-8" encoding was used to read the content and attempt to perform the validation, but this is likely to fail for all non-trivial documents.
Read the FAQ entry on character encoding for more details and pointers on how to fix this problem with your document.
Info No Character encoding declared at document level
No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
See this tutorial on character encoding for techniques and explanations.
Congratulations
The document located at <http://www.tonymarston.net/php-mysql/amortise.php> was tentatively checked as HTML 4.0 Transitional. This means that with the use of some fallback or override mechanism, we successfully performed a formal validation of it. In other words, the document would validate as HTML 4.0 Transitional if you changed the markup to match the changes we have performed automatically, but it will not be valid until you make these changes. The parser implementations we used for this check are based on OpenSP (SGML/XML).
Linking to this result
If you would like to create a link to this page (i.e., this validation result) to make it easier to revalidate this page in the future or to allow others to validate your page, the URI is < http://validator.w3.org/check?uri=http%3A%2F%2Fwww.tonymarst on.net%2Fphp-mysql%2Famortise.php> (or you can just add the current page to your bookmarks or hotlist).
Linking to this result
If you would like to create a link to this page (i.e., this validation result) to make it easier to revalidate this page in the future or to allow others to validate your page, the URI is < http://validator.w3.org/check?uri=http%3A%2F%2Fwww.tonymarst on.net%2Fphp-mysql%2Fconverter.php> (or you can just add the current page to your bookmarks or hotlist).
------------------
See can see the results in in
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.tonymarst on.net%2Fphp-mysql%2Famortise.php&charset=%28detect+auto matically%29&doctype=Inline&group=0&user-agent=W 3C_Validator%2F1.3
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.tonymarst on.net%2Fphp-mysql%2Fconverter.php&charset=%28detect+aut omatically%29&doctype=Inline&group=0&user-agent= W3C_Validator%2F1.3
Thanks.
|
|
|
|
|
|
| Re: sample v3.0.0 XHTML markup errors [message #3328 is a reply to message #3325] |
Mon, 14 January 2013 08:39 |
jjtoranzo2004
Messages: 261
Registered: September 2012
|
Senior Member |
|
|
Tony,
In page
http://www.tonymarston.net/sample/index.html
the nu validator
http://validator.nu/?doc=http%3A%2F%2Fwww.tonymarston.net%2F sample%2Findex.html
found the following errors:
Warning: The doctype did not contain the system identifier prescribed by the HTML 4.01 specification. Expected
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
From line 1, column 1; to line 1, column 50
[[instead of]]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">↩<html
Warning: The character encoding of the document was not declared.
http://www.tonymarston.net/sample/index.html
[[
I think it expect two width declarations, like
<colgroup>
<col width="150" />
<col width="500" />
</colgroup>
instead of
<colgroup width="150"></colgroup>
]]
Error: A table row was 2 columns wide and exceeded the column count established using column markup (1).
From line 21, column 53; to line 22, column 5
page</td>↩</tr>↩<tr>↩
Error: A table row was 2 columns wide and exceeded the column count established using column markup (1).
From line 27, column 33; to line 28, column 5
</a>.</td>↩</tr>↩<tr>↩
Error: A table row was 2 columns wide and exceeded the column count established using column markup (1).
From line 32, column 103; to line 33, column 5
</a>.</td>↩</tr>↩<tr>↩
Error: A table row was 2 columns wide and exceeded the column count established using column markup (1).
From line 39, column 43; to line 40, column 5
</a>.</td>↩</tr>↩<tr>↩
Error: A table row was 2 columns wide and exceeded the column count established using column markup (1).
From line 47, column 18; to line 48, column 5
</a>.</td>↩</tr>↩<tr>↩
Error: A table row was 2 columns wide and exceeded the column count established using column markup (1).
From line 54, column 60; to line 55, column 5
</a>.</td>↩</tr>↩<tr>↩
Error: A table row was 2 columns wide and exceeded the column count established using column markup (1).
From line 61, column 57; to line 62, column 5
</a>.</td>↩</tr>↩↩</ta
-------------------------------------------------
The W3C Markup Validation Service further states that:
Warning No Character Encoding Found! Falling back to UTF-8.
None of the standards sources gave any information on the character encoding labeling for this document. Without encoding information it is impossible to reliably validate the document. As a fallback solution, the "UTF-8" encoding was used to read the content and attempt to perform the validation, but this is likely to fail for all non-trivial documents.
Read the FAQ entry on character encoding for more details and pointers on how to fix this problem with your document.
Info No Character encoding declared at document level
No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
See this tutorial on character encoding for techniques and explanations.
The document located at <http://www.tonymarston.net/sample/index.html> was tentatively checked as HTML 4.01 Strict. This means that with the use of some fallback or override mechanism, we successfully performed a formal validation of it. In other words, the document would validate as HTML 4.01 Strict if you changed the markup to match the changes we have performed automatically, but it will not be valid until you make these changes. The parser implementations we used for this check are based on OpenSP (SGML/XML).
Thanks.
|
|
|
|
|
|
|
|
|
|
Goto Forum:
Current Time: Sun Dec 22 00:31:59 EST 2024
Total time taken to generate the page: 0.06626 seconds
|
Radicore Forum
Search
Help
Members
Register
Login
Home
