Dave Hay wrote:
What if you want, say,
logic:iterate id=category name=TraceForm property=categoryList
...
On html:radio name=category property=value value=on
indexed=true/
Off html:radio name=category property=value value=off
indexed=true/
I could be mistaken, but this seems related
to the issue I noticed recently,
which is that the property attribute (and
apparently, the name/property
pair, in the indexed case) is improperly
overloaded to serve two purposes,
I agree with you that there are many ways one might want to
That way the buttons SHOULD all have
the same name for each iteration, and
different one for the next one etc..
That was the thinking behind it.
Thanks for your quick and helpful response.
That is yet another reasonable interpretation of how
to map the collection to radio buttons.
There
Frank == Frank Lawlor [EMAIL PROTECTED] writes:
I could be mistaken, but this seems related
to the issue I noticed recently,
which is that the property attribute (and
apparently, the name/property
pair, in the indexed case) is improperly
overloaded to serve two
Maybe I'm misunderstanding how to use html:radio with
indexed, but it seems broken to me.
If I specify:
logic:iterate name=ListForm property=itemList id=item ...
...
html:radio indexed=true name=item property=contact ... /
then it generates code like:
input type=radio
Frank == Frank Lawlor [EMAIL PROTECTED] writes:
Frank Maybe I'm misunderstanding how to use html:radio with
Frank indexed, but it seems broken to me.
Frank If I specify:
Frank logic:iterate name=ListForm property=itemList id=item ...
Frank ...
Frank
\) [EMAIL PROTECTED]
cc:(bcc: David Hay/Lex/Lexmark)
Subject: Indexed html:radio is broken
Maybe I'm misunderstanding how to use html:radio with
indexed, but it seems broken to me.
If I specify:
logic:iterate name=ListForm property=itemList id=item ...
...
html:radio indexed=true name
7 matches
Mail list logo
