You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How can one make Passman match on a page with a username but no password field? My bank has a page for username and then a second page where password and challenge questions must be answered.
Passman webextension in firefox does not detect form due to error (form ignored (https://www.mycardstatement.com/#/) -- no password fields.) Only username field is present. Password and challange questions are on next page after username is submitted.
no further action avaiable
Expected behaviour
Tell us what should happen
passman should detect username field and proceed to populate
Actual behaviour
Tell us what happens instead
nothing happens, form not detected
Configuration
Operating system:
windows 10
Browser:
firefox
Extensions that might cause interference:
none known
Passman version:
2.3.1335 Extension version:
2.1.1
Nextcloud version:
22.2.2
Browser log
Browser log
```
Insert your browser log here, this could for example include:
How can one make Passman match on a page with a username but no password field? My bank has a page for username and then a second page where password and challenge questions must be answered.
The error from debug:
(form ignored (https://www.mycardstatement.com/#/) -- no password fields.)
Steps to reproduce
Expected behaviour
Tell us what should happen
passman should detect username field and proceed to populate
Actual behaviour
Tell us what happens instead
nothing happens, form not detected
Configuration
Operating system:
windows 10
Browser:
firefox
Extensions that might cause interference:
none known
Passman version:
2.3.1335
Extension version:
2.1.1
Nextcloud version:
22.2.2
Browser log
Browser log
``` Insert your browser log here, this could for example include:a) (form ignored (https://www.mycardstatement.com/#/) -- no password fields.)
b)
c) ...
The text was updated successfully, but these errors were encountered: