On Fri, 26 May 2006, Matthew Raymond wrote:
Henri Sivonen wrote:
The WF2 spec does not say anything about filtering autocomplete lists
on pattern and Opera 9 does not do it. However, autocomplete entries
that would fail form validation are not particularly useful.
I suggest saying
Ian Hickson wrote:
Could you give an example of this? It seems like the common cases, like
picking named values, would be handled by label= vs value=:
1:input type=number name=gauge list=gauges min=0 step=any
datalist id=gauges
option label=Z value=220
option label=N
On Thu, 24 Aug 2006, Matthew Raymond wrote:
Yeah, I suppose that would be fine, except for extremely rare cases
where the value absolutely has to be outside the pattern. The following
don't have fixed-length numeric values, for instance:
| datalist id=math
| option label=i
On Thu, 4 May 2006, Henri Sivonen wrote:
The WF2 spec does not say anything about filtering autocomplete lists on
pattern and Opera 9 does not do it. However, autocomplete entries that
would fail form validation are not particularly useful.
I suggest saying that potential autocomplete
On Fri, 26 May 2006, Henri Sivonen wrote:
On May 26, 2006, at 09:23, Matthew Raymond wrote:
Henri Sivonen wrote:
The WF2 spec does not say anything about filtering autocomplete lists
on pattern and Opera 9 does not do it. However, autocomplete entries
that would fail form validation
Henri Sivonen wrote:
The WF2 spec does not say anything about filtering autocomplete lists
on pattern and Opera 9 does not do it. However, autocomplete entries
that would fail form validation are not particularly useful.
I suggest saying that potential autocomplete items (whether
The WF2 spec does not say anything about filtering autocomplete lists
on pattern and Opera 9 does not do it. However, autocomplete entries
that would fail form validation are not particularly useful.
I suggest saying that potential autocomplete items (whether supplied
by the UA itself or
