# HG changeset patch # User paulb # Date 1122071046 0 # Node ID 89ed1f93b0d43ea1e32be923584c04101aa3b028 # Parent b73bc13d53c0cb046cda7dedef8bf5f89e28af7f [project @ 2005-07-22 22:24:06 by paulb] Fixed link. diff -r b73bc13d53c0 -r 89ed1f93b0d4 docs/multivalue.html --- a/docs/multivalue.html Fri Jul 22 21:34:01 2005 +0000 +++ b/docs/multivalue.html Fri Jul 22 22:24:06 2005 +0000 @@ -50,7 +50,7 @@ style="font-weight: bold;">multiple="multiple">
<option template:element="type-enum" template:expr="@value-is-set" template:expr-attr="selected"
template:value="@value" value="{@value}" />
</select>
</p>
<p>
Itself containing more items:
</p>
<p template:element="subitem">
Sub-item: <input template:attribute="subvalue" name="{template:this-attribute()}" type="text" value="{$this-value}" />
<input name="remove2={template:this-element()}" type="submit" value="Remove" />
</p>
<p>
<input name="add2={template:this-element()}" type="submit" value="Add subitem" />
</p>
</div>
<p>
<input name="add={template:this-element()}" type="submit" value="Add item" />
</p>

<!-- Template text between the interesting part and the end. -->

</form>
</body>
</html> -

From the previous single-valued case, +

From the previous single-valued case, some crucial changes have been made:

  1. The select element remains mapped onto the type