- From: Matthew Raymond <mattraymond@earthlink.net>
- Date: Thu, 01 Jul 2004 22:58:35 -0400
I was just thinking that perhaps the best solution would involve
making "ignore" an attribute instead of an element. Any element with
this attribute would act in the same manner as I described with the
<ignore> element. With that idea, I introduce the following example:
=== Sample #8 ===
WF2-ONLY:
<input type="text" name="combo1" value="something" list="select1" />
<select ignore="true" id="select1" data="options.xml" />
...OR...
<input type="text" name="combo1" value="something" list="select1" />
<select ignore="true" id="select1">
<option>First Option</option>
<option>Second Option</option>
<option>Third Option</option>
</select>
WF2 + LEGACY:
<input type="text" name="combo1" value="something" list="select1" />
<label ignore="true" for="select1"> or select from this list: </label>
<select ignore="true" id="select1" name="combo1">
<option>First Option</option>
<option>Second Option</option>
<option>Third Option</option>
</select>
Pros:
Degrades to both a text box and a drop-down list.
Input has a specific type.
Uses the existing |type| attribute of <input> for input typing.
No abusive markup.
No new elements.
The |ignore| attribute helps prevent abuse of repetition templates,
because it's easier to remember 'ignore="true"' than
'repeat="template" repeat-start="0"'.
Cons:
Legacy UAs submit multiple values to the server.
Requires a new |ignore| and |list| attributes.
Received on Thursday, 1 July 2004 19:58:35 UTC