Skip to content
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.

Commit

Permalink
Added guidance for how UI filtering for suggestions should work. (#848)
Browse files Browse the repository at this point in the history
  • Loading branch information
adanilo authored and travisleithead committed Mar 30, 2017
1 parent 4154267 commit e205f9d
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions sections/semantics-forms.include
Original file line number Diff line number Diff line change
Expand Up @@ -6714,6 +6714,9 @@ You cannot submit this form when the field is incorrect.</samp></pre>
User agents are encouraged to filter the suggestions represented by the <a>suggestions source element</a> when the number of suggestions is
large, including only the most relevant ones (e.g., based on the user's input so far). No precise
threshold is defined, but capping the list at four to seven values is reasonable.
User agents that perform filtering should implement substring matching on the <{option/label}> attribute.

<p class="warning">Existing user agents filter on either <{option/value}> or <{option/label}> so the behavior may be inconsistent.</p>

How user selections of suggestions are handled depends on whether the element is a control
accepting a single value only, or whether it accepts multiple values:
Expand Down

0 comments on commit e205f9d

Please sign in to comment.