Hello,

I am trying to develop valid XHTML app, and was progressing quite well
until today, when I noticed that some of my form pages are invalid.

I am using quixote 1.0-1 from Debian Sarge.

W3C validator barks on pages with OptionSelectWidget and/or if
FORM_TOKEN is used. Both using default form renderer.

OptionSelectWidget places  inside 
>       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 "
" or "
") inside
>       an inline element (such as "", "", or "").
>
>   2.
>
>       /Line 465
>       ,
>       column 74/: end tag for "noscript" which is not finished
>
>       |...t" name="" value="apply"
>       />*
|
>
>       Most likely, You nested tags and closed them in the wrong order.
>       For example 
...
 is not acceptable, as  must be
>       closed before 
. Acceptable nesting is: 
...
>
>       Another possibility is that you used an element (e.g. 'ul')
>       which requires a child element (e.g. 'li') that you did not
>       include. Hence the parent element is "not finished", not complete.
>

And if FORM_TOKEN=True then valid forms become invalid because of an
 inside 
:

>   1.
>
>       /Line 454
>       ,
>       column 103/: 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
>
>       |..."_form_id" value="cf7b304b0ec736be" /*>*
       colspan="3">* = <|
>
>       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 "
" or "
") inside
>       an inline element (such as "", "", or "").
>

Both validated against XHTML 1.1.

Any plans to fix it in next version?

Thanks!

--Kirill


reply