Describe the bug
Is it intentional that autocomplete on inputs won't work? Login and password for example.
To Reproduce
Steps to reproduce the behavior:
native|<sl-input autocomplete="on">
-|-
Use native input in html form, select browsers saved login - the password is autofilled|Password not filled, saved logins not used
|
Expected behavior
Would be nice, if saved logins are provided and used too if clicked
Desktop (please complete the following information):
Would be nice to know, if this is a bug or a feature / expected behavior 馃槈
It's intended to work, and I've seen it work first hand many times. In fact, it worked so well that a composed <sl-input> inside of <sl-select> was getting autocompleted (#266). 馃槀
Can you post a test case?

The suggestions are shown, this is correct, but the password is not filled with the value which is stored in browser for the login field.
With <sl-input> you have to click / select the correct password entry manually from browser suggestions.
I will try to create a codepen for this later 馃槈
Here we go:
https://codepen.io/trailsnail-the-lessful/pen/wvWRmmK
testuser in native Login and test in native password fieldtestuser

<sl-input name="login">

It seems, that the fields aren't linked to browsers saved logins

Hope this helps 馃嵒
Possibly related: https://bugs.chromium.org/p/chromium/issues/detail?id=649162
Seems you are right. Thanks for investigation.
@staabm fyi
But AFAIR FF had the same issue, no?
But AFAIR FF had the same issue, no?
What's this? https://bugzilla.mozilla.org/show_bug.cgi?id=1629226
While searching for matching topics, the Shadow Dom seems to be responsible for many other strange behaviors 馃ぃ
Seems this is still an issue with Safari. 馃槥 Guess I'll need to use a standard light DOM input for username/password fields.