I have two websites that I cannot get the autofill to work for. I suspect it is the same problem for both - they have two page forms - the first is a username, which doesn’t autofill and the second page is the password, which does autofill.
Can anyone explain/guide me on how to get these to autofill the username on this first page?
https://onboarding.betashares.com.au/
Thanks!
The username input does not have ID or name, so the form can’t autofill
Ah ok that sucks then. Firefox and my phone can both auto fill it so it’s possible somehow, but sounds like Kee can’t.
The username input does not have ID or name, so the form can’t autofill
Yes it does. Indeed both do. Inspect element reveals the username input on the ubank site to be:
<input sp-number-mask=“” class=“sp-input__input ng-tns-c3250689687-1 sp-input__input–lowercase ng-untouched ng-pristine ng-invalid ng-star-inserted” id=“username-hash-ba2f7780-5bd5-11f0-832e-6b432e145053” type=“text” autocomplete=“username” autocapitalize=“none” placeholder=“Email or mobile number” required=“” aria-invalid=“false” sp-automation-id=“input-username”>
and on the betashares site:
<input id=“onboardingForm_email” type=“email” placeholder="hello@emailaddress.com" class=“text-left cursor-pointer w-full py-3 border-none bg-transparent !outline-none” data-testid=“text-field_input” autocomplete=“username”>
I have the same problem as Ned with a couple of sites – username on first page doesn’t autofill, password on second does – but haven’t investigated them (yet)… 
Try adding an include configuration for each site. betashares should work if you use its id, you can try the other site too but perhaps that UUID in the ID will change in future and thus prevent this approach from working for very long.
Ultimately, we need to work on Consider DOM autocomplete attribute values for form selection and field fill prioritisation · Issue #337 · kee-org/browser-addon · GitHub which will probably improve the behaviour for both of these examples.