Angular 2 - Form is invalid when browser autofill

Question

I have a Login Form which has email and password fields.

I've chosen for browser autofill.

The problems is: When browser autofills login form, both fields are pristine and untouched, so the submit button is disabled.

If I click on disabled button, it enables and fires submit action, what is nice. But the default disabled aspect is pretty bad what can make some users disappointed.

Do you have some ideas about how to deal with?

@JohnDizzle: Did you guys able to get it work? if yes then how? :) — Denish, Feb 27 '18 at 08:39
@Denish No, I must disappoint you. This seems to be an open problem for everyone in the community... — JohnDizzle, Feb 27 '18 at 09:38
@Denish, If you have a reactive form, then something like [disabled]="user.invalid" should work — Vega, Apr 04 '18 at 17:43
It might be related to this issue here: The autofill values only become available after user interacts with the form: https://github.com/angular/material2/issues/3414 — Kristjan Liiva, Aug 31 '18 at 09:59

score 5 · Answer 1 · answered Jun 06 '19 at 08:26

5

I solved it by also checking if the form was touched when displaying error messages. So, for example, the submit button looks like this

<input type="submit" class="btn btn-default" [disabled]="loginFormGroup.invalid && loginFormGroup.touched" />

answered Jun 06 '19 at 08:26

Teun

165
1
7

2

So the button will still be activated if the fields are empty when the page load with this solution – Mattew Eon Jul 15 '22 at 15:34
This is the most elegant, and error-proof declarative solution, imho – Janos Dec 06 '22 at 08:22

score 4 · Answer 2 · edited Jul 17 '22 at 02:26

4

I seem to have solved this by just simulating a click on the page AfterViewInit.

Js :

public ngAfterViewInit(): void {
    document.querySelector('body').click();
}

With JQuery :

public ngAfterViewInit(): void {
    $('body').click();
}

Chrome 67.0.3396.99, Angular 5.1.0

edited Jul 17 '22 at 02:26

Mattew Eon

1,722
1
21
38

answered Jun 27 '18 at 06:19

Arg0n

8,283
2
21
38

score 2 · Answer 3 · answered Aug 12 '18 at 11:50

I solved this problem with the ChangeDetectorRef Provider.
Simply do a manual detectChanges() before you check if the input is valid.

If you aren't able to check after a button click, then hear on the Input-Event of the Input-Element with the event-binding (input)=changedetectorfunc() and call the changeDetector in this function.
Therefore it must work.
Hope, it helps you.

useful links:

Best wishes

score 0 · Answer 4 · answered Oct 08 '21 at 16:42

There are two ways to solve this problem

Use CSS pseudo class -webkit-autofill it will detect the autofill.

https://developer.mozilla.org/en-US/docs/Web/CSS/:aut

Use AutofillMonitor package from angular/cdk module which monkey patch the Validators Since RequiredValidator is not able to acknowledge autofill input.

https://gist.github.com/kherock/fad4c320c5894ec68373588e338955c5

score -2 · Answer 5 · answered Mar 26 '17 at 09:55

-2

I had the same problem.

I solved it by: - removing the Validators.required validator for the password field in the component - using the <input ... required ...> directive at the tag in the template

answered Mar 26 '17 at 09:55

Dr. Simon Harrer

1,954
1
15
26

score -2 · Answer 6 · edited Nov 20 '18 at 20:14

this is not the best practice for code but it will work for sure-

if you are having two way binding then its very easy task just check for length of both textbox if it is greater then zero then return false else return true and call the method in disabled attribute. Method-

    validcheck() {
         return username.length <= 0 || password.length <= 0;     
    }

and call the method inside button disabled attribute

    <button [disabled]="validcheck()">Submit</button>

score -3 · Answer 7 · answered Feb 03 '17 at 22:40

Had the same problem too. I'm not sure if this is the best way, but I was able to get it to work by adding AfterViewChecked

import { Component, AfterViewChecked } from "@angular/core";

export class LoginComponent implements AfterViewChecked {
    // Beware! Called frequently!
    // Called in every change detection cycle anywhere on the page
    ngAfterViewChecked() {
        console.log(`AfterViewChecked`);
        if (this.usr.userName) {
            // enable to button here.
            console.log("found username in AfterViewChecked");
        }
    }
}

or you might be able to try Angular2's other Lifecycle Hooks https://embed.plnkr.co/?show=preview

That will enable the button but the form itself will still be invalid, so submission will not go through. — Euridice01, Feb 13 '17 at 05:42

score -3 · Answer 8 · answered Mar 29 '18 at 22:54

According to the offical docs

"pristine" means the user hasn't changed the value since it was displayed in this form

So if you have a validation in your form it's a better approach to check if the form is "valid" or "invalid"

<button [disabled]="formName.invalid">Submit</button>

So it doesn't matter if the form is pristine or not.

Angular 2 - Form is invalid when browser autofill

8 Answers8

There are two ways to solve this problem

Linked