[Fatalist_ma]

I'm not sure adding more concrete UI elements is the way to go, browsers are too complex as at is, which makes it extremely hard to develop them unless you have as much resources as Google. And what happens after 10 years when new UI trends become popular and we need new ui elements? We don't want to break the web, we can't just remove old stuff, so we'll need to keep adding and adding.

I think a much more important endeavour is to make the browser more extensible,(like what CSS Houdini is trying to do), so you can create any kind of crazy interfaces(without having to abandon css/html completely and drop down to canvas/webgl).

[Ashanmaril]

> And what happens after 10 years when new UI trends become popular and we need new ui elements?

Design trends change, but the basic components that make up form elements have remained the same. We still have buttons, text fields, check boxes, radio buttons, etc. Those aren't going anywhere.

[Macha]

Well, depends on if your consider a slider a check box and a sequence of rows of which one is highlighted a radio button.

[arkitaip]

Fields with autocomplete have been around for decades. By having them in a spec, we don't have to reinvent the UI element poorly on every single site.

[somethingAlex]

I just don't think browsers are in a good position to implement advanced features like this, though. They are too general of a tool to be opinionated and if you aren't going to be opinionated I don't see how javascript isn't the answer.

What kind of autocomplete do you want? Which algorithm? What's the threshold if you're using some kind of "string distance" metric? What do you want to do style wise when you match portions of strings? What optimizations should be made for your specific case?

I don't see how a web browser is in a better position to make these types of features compared to a javascript library / web assembly.

[sleepyhead]

All autocomplete implementations has different behaviour. It is not as basic as other fields such as text and checkbox. The same applies to date input which still often have custom implementations because the browser based input has ux issues or offers limited behaviour changes.