RESOLVED CONFIGURATION CHANGED Bug 27247
Master bug of datalist element and list attribute implementation
https://bugs.webkit.org/show_bug.cgi?id=27247
Summary Master bug of datalist element and list attribute implementation
Kent Tamura
Reported 2009-07-14 01:50:23 PDT
I'll make a patch to support for `list' attribute. The UI will be like http://docs.google.com/View?id=dch3zh37_0cf8kc8c4
Attachments
Screenshot produced by actual code (11.77 KB, image/png)
2009-07-27 21:23 PDT, Kent Tamura
no flags
Reference patch (25.53 KB, patch)
2009-07-30 03:04 PDT, Kent Tamura
tkent: review-
Kent Tamura
Comment 1 2009-07-27 21:23:50 PDT
Created attachment 33600 [details] Screenshot produced by actual code I have almost completed the code. Because the patch is large, I'll split it into some bugs.
Anthony Ricaud
Comment 2 2009-07-29 05:18:08 PDT
Kent Tamura
Comment 3 2009-07-29 17:12:00 PDT
(In reply to comment #2) > It doesn't look very native. A NSComboBox on MacOS feels nicer : > http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Classes/nscombobox_Class/Reference/Reference.html Do you think NSComboBox is nicer for <input type=search> or <input type=number> ?
Kent Tamura
Comment 4 2009-07-30 03:04:19 PDT
Created attachment 33765 [details] Reference patch This is a patch without ChangeLog and tests, for reference. I'll submit a complete one after all dependent patches are landed.
Peter Kasting
Comment 5 2009-08-04 15:59:35 PDT
dhyatt was working on <datalist> support, he should be CCed on all bugs about it
Kent Tamura
Comment 6 2009-08-18 17:14:54 PDT
Does anyone have an idea of better UI for list attribute support? If not, I'll update the patches and request to review them.
Aryeh Gregor
Comment 7 2010-01-21 16:52:44 PST
FWIW, Opera displays this the same as autocomplete suggestions. In other words, there's a dropdown that automatically appears when the user focuses the field and starts typing, and he can use the arrow keys or mouse to select an item from it. This is nice if you're trying to use <datalist> to implement search suggestions -- a combobox UI would be unusable for that use-case. Related WHATWG thread: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-January/024794.html
Kent Tamura
Comment 8 2010-01-21 16:58:38 PST
(In reply to comment #7) I don't think the UI of Opera is the best. It's hard for users to know that a field has choices provided by the page author.
Aryeh Gregor
Comment 9 2010-01-21 17:02:51 PST
That's what's wanted for search suggestions -- they should look like browser suggestions. However, it's not wanted for comboboxes. It's not clear to me which way is "right". I've suggested to the WHATWG that perhaps a separate JS-only API should be specced for search suggestions, leaving <datalist> more clearly for comboboxes, but I expect it will be a while before I get a response on that.
Aryeh Gregor
Comment 10 2010-01-22 13:26:07 PST
Maciej suggested that for type="text", it should use a native combobox widget, while for type="search" it should look like search suggestions: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-January/024799.html Does that make sense to you?
Kent Tamura
Comment 11 2010-01-24 23:18:19 PST
Hmm, the idea of type-specific appearance makes sense. So, we'll make the followings for <datalist> and list attribute? No special UI (text field) ==> Native combo-box Type=search ==> like search-suggestions Type=range ==> Markers Type=color ==> In the color chooser dialog? Type=number ==> Additional menu button (my original proposal) date/time types ==> ditto
Ridley Combs
Comment 12 2011-05-07 19:56:26 PDT
Agreed. Reference Safari's Google Search box for type=search. (In reply to comment #11) > Hmm, the idea of type-specific appearance makes sense. > > So, we'll make the followings for <datalist> and list attribute? > > No special UI (text field) ==> Native combo-box > Type=search ==> like search-suggestions > Type=range ==> Markers > Type=color ==> In the color chooser dialog? > Type=number ==> Additional menu button (my original proposal) > date/time types ==> ditto
Dongwoo Joshua Im
Comment 13 2011-09-21 23:45:03 PDT
Is this patch still going on? It looks almost done, but why it stops here?
Jon Lee
Comment 14 2011-09-23 13:36:21 PDT
Bronislav Klucka
Comment 15 2011-09-23 15:07:19 PDT
(In reply to comment #14) > <rdar://problem/10069956> Hi, I'm trying to stay informed... what does such element/URN/scheme means? How can I look at such content?
Darin Adler
Comment 16 2011-09-23 15:14:40 PDT
Those URLs are for Apple’s internal bug tracking system, Radar. For the most part, they are not useful to anyone who does not work for Apple except to communicate with people who do.
Tobias Tom
Comment 17 2013-10-17 06:19:30 PDT
I assume this issue is still blocked by some stuff in radar?
Darin Adler
Comment 18 2013-10-17 10:57:27 PDT
(In reply to comment #17) > I assume this issue is still blocked by some stuff in radar? I don’t think so. Not even sure what that question means.
Teun
Comment 19 2014-03-05 08:56:39 PST
Please make this very useful feature happen.
Domenic Denicola
Comment 20 2016-10-28 09:30:46 PDT
The spec has been updated with some concrete suggestions on display and string matching that might be helpful for those implementing this: https://html.spec.whatwg.org/multipage/forms.html#attr-input-list
Alexey Proskuryakov
Comment 21 2018-08-23 09:50:39 PDT
*** Bug 188857 has been marked as a duplicate of this bug. ***
Javan Makhmali
Comment 22 2019-10-17 11:43:19 PDT
Related: I just reported bug 203116, "Native text substitutions interfere with HTML <datalist> options resulting in crash"
Javan Makhmali
Comment 23 2019-10-17 12:32:53 PDT
I would like to see bug 201768, comment 2 added to this list as well.
Ahmad Saleem
Comment 24 2022-09-20 13:07:45 PDT
All dependent bugs are closed. Marking as "RESOLVED CONFIGURATION CHANGED". Thanks!
Note You need to log in before you can comment on or make changes to this bug.