We have a page where a button click routes to new page using angular routes. The first page has change password form and when we click on submit button, the pop-up comes up.
Before entering the username and savin, the pop-up is disappearing once the angular route loads up. Please advice.

Existing multi-value attributes (rel, aria-labelled-by, aria-described-by, class`) are using space-separated lists, not comma-separated lists. I would make sense to be consistent here.

Side note: this allows using such attribute in a CSS selector too thanks to the ~= operator

The title says it all. Add a guideline about data-form-type="other" as a "ignore" mechanism.

The "routing number" or "bank code" part of bank account number needs to be better defined.

The walmart example is said to be an example for a login form, but the screenshot is for the Create account form, which looks more like a register case to me.

We have a three step form to reset password if user forgets.
Login screen (click on forgot password) -> User verification form (enters username and other data) -> Authentication form (OTP etc.,) -> Password reset form (New and confirm new password).

In this flow, when we enter the new password, dashlane prompts(chrome extension) to store password but the login/username remains unpopulated.

I appreciate your effort to write a spec for enhancing the semantics of Web forms used by Web extensions such as Dashlane, as opposed to just publishing it in form of API reference for the browser extension. Thanks! However, I have a question:

The spec says:

The data-form-type attribute carries type information about the form carrying the attribute. It is an unordered list of comma-separated case-insensitive values. Its default value is "other".

I have noticed in my web app that the Dashlane browser extension to Chrome adds its autocompletion to a regular <input type="text"> without a data-form-type attribute.

Does it mean that Dashlane web extension does not follow the spec closely, or should the spec be updated?

If needed, I can provide the actual code that triggered the extension by email.