Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome: Login on (some) angular-JS based pages only possible after adding and removing a char in username and password field (workaround) #41

Open
amenk opened this issue Mar 24, 2017 · 5 comments

Comments

@amenk
Copy link
Collaborator

amenk commented Mar 24, 2017

http://debugmail.io
https://www.steuer-web.de/

Testcase:

  1. Login and save credentials
  2. Logout
  3. Come back
  4. Try to auto-login -> does not work
  5. in user and password field, add a space manually and delete it again
  6. Login works
@amenk
Copy link
Collaborator Author

amenk commented Jul 9, 2017

The both use angular JS

@amenk amenk changed the title Chrome: Login only possible after adding and removing a char in username and password field (workaround) Chrome: Login on (some) angular-JS based pages only possible after adding and removing a char in username and password field (workaround) Jul 9, 2017
@amenk
Copy link
Collaborator Author

amenk commented Jul 9, 2017

@amenk
Copy link
Collaborator Author

amenk commented Jul 9, 2017

angular/angular.js#3133

@amenk
Copy link
Collaborator Author

amenk commented Jul 9, 2017

In some cases it seems to work, for example in a new chrome profile without any other extensions it works most of the time - but sometimes it still does not ... while in my normal chrome profile with tons of extensions I can always reproduce.

If it is the same problem as in describe int he links, I think we need to send an "input" event in addition to the key-presses.

@amenk
Copy link
Collaborator Author

amenk commented Jul 9, 2017

Seems to not be really related to other extensions .. is just not clearly reproducible. Now with the current dev-master of the passopolis extension in my normal profile the problem seems to be not reproducible. Swichting back to the chrome-store version 2015.9 it seems to come back but only some times ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant