ngList is misstaken for the list attribute

[jimmywarting]

list attribute is used on input elements that can show auto completion in combination with <datalist>
You could expect (without reading the docs) that ngList would do some magic auto completion awesomeness that would generate a <datalist> with a unique id to match the input. And show some suggestion when you focus on the field.

I would suggest we remove the ngList and when multiple attribute is present it will return the value as an array
the new (working?) spec says that "multiple" attribute is supported on all inputs but are only used for <select> file, email and range inputs.

Then maybe later we could build some awesome auto completion around the ngList in the future? 👍

I think we should honor multiple attribute more
I wouldn't like the fact that I would have to use ng-list on email to get an array from the model. multiple attribute must also be there to support the native behavior... so why not only use multiple?

<input multiple ng-model="websites"> default delimiter to , (like email)
<input multiple ng-model="websites"  ng-model-option="{delimiter: "|"}> changed delimiter to | 

[btford]

So your suggestion is to:

1. Rename the current ngList
2. Implement a new feature called ngList aligned with the <datalist> element

I agree that ngList is perhaps a bit confusing, but this would be a significant breaking change for (in my opinion) not enough benefit to justify the change.

[shahata]

There's another suggestion here to start supporting the multiple attribute. This is covered by a PR #8987

[jimmywarting]

1. i was more thinking of removing it completely in honor of the multiple attribute. feat(input): support multiple attribute for email #8987 did it this ways to make a ngList-ish behavior
   to solve the "optional delimiter that should be used to split the value." you could use the ngModelOption like i showed you
   (so it would be like renaming ngList to multiple without the delimiter option - since it will now be a boolean)
2. Yes

It would indeed be a breaking change. but i would rather update my code to use the multiple attribute instead. it has more valuable meaning
multiple is already used in input[type=file/email/range] and select
(folks knows what it means and what it dose - allows you to select more then one)

[Binvention]

If this change does occur I think it's important to bring up the issue described in this issue #13714 which talks about the current problem with ng-list and an empty delimiter