[XHTML] Błędy w użyciu traget, textarea, onsubmit, onclick
: ndz gru 11, 2005 7:29 pm
Oto błędy w validacji mojej strony....nie rozumiem , o co chodzi w używaniu traget, textarea, onsubmit, onclick oraz uid# Error Line 393 column 50: document type does not allow element "textarea" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag.
...ow:hidden; width:135px; margin: 2px;">zadaj pytanie lub opisz problem</textar
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>").
# Error Line 400 column 35: 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.
style="width:135px; margin: 2px;" />
# Error Line 405 column 53: 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.
style="width:70px; margin: 2px; margin-bottom:2px;" />
# Error Line 406 column 6: end tag for "form" which is not finished.
</form>
Most likely, You nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, <head> generally requires a <title>, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
# Error Line 417 column 59: there is no attribute "target".
....reporter.pl/porady/?pp=JJ09" target="_blank"><img src="buttons/webreporter.g
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.
# Error Line 418 column 45: there is no attribute "traget".
...ef="http://www.lap.pl/?p=112" traget="_blank"><img src="buttons/lap.gif" alt=
# Error Line 433 column 66: there is no attribute "target".
...ttp://www.sonda.pl/vote.php3" target="sondaplwin" OnSubmit="ResultWindow('too
# Error Line 433 column 88: there is no attribute "OnSubmit".
...e.php3" target="sondaplwin" OnSubmit="ResultWindow('toolbar=no,scrollbars=yes
# Error Line 451 column 48: there is no attribute "OnClick".
...tp://www.sonda.pl/wait.php3" OnClick="javascript:window.open('http://www.sond
# Warning Line 451 column 115: cannot generate system identifier for general entity "uid".
...//www.sonda.pl/wyniki.php3?id=323362&uid=200644', 'sondaplwin', 'toolbar=no,s
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.
# Error Line 451 column 115: general entity "uid" not defined and no default entity.
...//www.sonda.pl/wyniki.php3?id=323362&uid=200644', 'sondaplwin', 'toolbar=no,s
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
# Warning Line 451 column 118: reference not terminated by REFC delimiter.
...ww.sonda.pl/wyniki.php3?id=323362&uid=200644', 'sondaplwin', 'toolbar=no,scro
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
# Warning Line 451 column 118: reference to external entity in attribute value.
...ww.sonda.pl/wyniki.php3?id=323362&uid=200644', 'sondaplwin', 'toolbar=no,scro
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
# Error Line 451 column 118: reference to entity "uid" for which no system identifier could be generated.
...ww.sonda.pl/wyniki.php3?id=323362&uid=200644', 'sondaplwin', 'toolbar=no,scro
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
# Info Line 451 column 114: entity was defined here.
...://www.sonda.pl/wyniki.php3?id=323362&uid=200644', 'sondaplwin', 'toolbar=no,
