1291179 - The html datalist search not working like chrome?

Status: RESOLVED WORKSFORME

(Core :: DOM: Core & HTML, defect, P5)

Description

[ranjan653]

Attachment: datalist_issue.png

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Steps to reproduce:

Please go through the link for example.
http://www.w3schools.com/tags/tryit.asp ... 5_datalist

If you type "i" in the text box for chrome shows one record i.e Internet Explorer
But firefox displays Internet Explorer, Firefox and Safari.




Actual results:

If you type "i" in the text box for chrome shows one record i.e Internet Explorer
But firefox displays Internet Explorer, Firefox and Safari.


Expected results:

If you type I the expexted result should be "Internet Explorer" like Chrome browser

Comment 1

[ranjan653]

Please solve this issue as high priority

Comment 2

[Tooru Fujisawa [:arai]]

(This is not any of crashes, loss of data, severe memory leak, so changing back to normal severity.
 https://bugzilla.mozilla.org/page.cgi?id=fields.html#bug_severity )

Apparently, Chrome, Edge and IE11 use prefix match, and Firefox uses substring match.
(WebKit doesn't support it)

I don't see anything in the spec that defines the matching algorithm for list attribute tho, it might be nice to use same algorithm as other browsers.
https://html.spec.whatwg.org/multipage/forms.html#the-datalist-element
https://html.spec.whatwg.org/multipage/forms.html#attr-input-list

Comment 3

[ranjan653]

What can be done so that i can get the exact result like chrome?

Comment 4

[Olli Pettay [:smaug][[e-mail]]]

So the data list is used as an input for autocomplete and that code does substring match.
I'd say the behavior Gecko has is quite reasonable - works way better with certain types of list, like
country names, or lists containing first and second name etc.
I wonder if the datalist could have some attribute giving UA some hint how the data should be used.
Perhaps worth to file a spec bug: https://github.com/whatwg/html/issues/new

Comment 5

[Domenic Denicola]

The spec has been updated to suggest substring match: https://html.spec.whatwg.org/multipage/forms.html#attr-input-list

However, the substring match should be searched in both the value and the label, whereas Firefox only searches (and displays) the label. See bug #869690.

Also of note, since this bug was filed, Chrome was updated to use substring matching. (But, per spec, on both the value and label.)

Comment 6

[Jonathan Watt [:jwatt]]

Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)

Comment 7

[Mike Taylor [:miketaylr]]

Given Comment #5, let's close here. The remaining issue described by Domenic is covered in Bug 869690 (I think).