You mean why would somebody build custom inputs? We need our inputs on Autocode to do a whole ton of custom stuff; support emoji insertion, allow for an autocomplete dropdown, support typeahead autocomplete, have multiple layers for syntax highlighting (code editor).

So we roll our own components for a lot of this stuff. We don't have problems with every password manager; the raw HTML input element is still there. I think it's probably an easy fix, we just gotta look into it.

None of those use cases apply for authentication though right? Or are people using emojis for logins now? Even if they were, standard browser form input I’m sure would handle them fine natively.

(1) Design systems and components. We'd rather use the same thing everywhere, if possible. (Unless of course, it disrupts user login and end-user experience... which is why we'll look into making it better!)

(2) I actually think this can be fixed with a few HTML attribute changes but I won't know for sure until I dig in. If you can imagine, we have a laundry list of items piling up to take care of :)

For (2), you may find the section 'Other useful autocomplete values' from this article helpful:

https://www.twilio.com/blog/html-attributes-two-factor-authe...

Discussed on HN: https://news.ycombinator.com/item?id=22022106

This makes sense to me. Thanks for the response~

Learned a lot