[Bug 9785] Add a "filter" attribute. If set, the user agent will filter the datalist. If not, filter won't be filtered automatically (unless you do some sort of filtering by javascript or/and server-side)

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9785


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |NEEDSINFO




--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-09-10 09:16:36 ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale:

Currently the spec doesn't say if there should be filtering or not — it just
says that these are the suggested values and leaves the UI to the UA.

The idea here is to provide a combo box, not to provide a "Google suggest"-like
interface. The latter would probably be better handled by a pure JS solution
with callbacks.

I would recommend that browser vendors play with offering different attributes
(using the vendor-extension syntax!) to experiment with what the best way to
extend this feature would be, and report back. We can then update the feature
appropriately.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 10 September 2010 09:16:38 UTC