[TYPO3-content-rendering] data[tt_guest] & wrap="virtual" dont validate

[JoH]

>> Is this a guess or does this really resolve the problem?
>
> it works like this...
> _BUT_ there is another problem.
> see:
>
http://validator.w3.org/check?verbose=1&uri=http%3A//www.lingoist.com/test/test.php
>
>    <label for="data&#91;
>    <label for="data[
>
> and
>
>    id="data&#91;
>    id="data[
>
> all four are invalid...thats not nice...so I think there is no
> solution _at all_ for this problem... (except dropping the label tag
> and the id attribute) :(
> if the id attribute is dropped than the javascriptvalidation will
> cause errors...(this is a guess as i didnt look closer at it ;)

You forgot the main solution:
Dropping the so called "validation" of HTML code and doing things the way
they are working.
Just the fact that a "validator" says, this character is "not allowed"
anymore doesn't mean it will do harm to any user coming to a site using this
code.
(BTW: Is there any reason, why one should not use those characters for "id"
or "for"? - And don't tell me: Because it is written ...!)

AFAIK the "data[whatever][will_be]" construct is needed to fill arrays in
the backend.
So the question is: Is it worth to rewrite the whole FORM-array concept just
to have the code "validated"?
If yes, you might add some hidden fields instead of the arrays do determine
into which table the data should be written.
You will loose a lot of flexbility and comfort. Since you won't be able to
use different tablenames in one form.

Or - as Masi mentioned before - you will have to replace the characters with
some "funky stuff" that will never be part of a table-/fieldname.

All of these seems very weird to me and again it proves how far from reality
those "standards" are.

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your knob sometimes!)
Dieter Nuhr, German comedian
openBC: http://www.openbc.com/go/invuid/Jo_Hasenau