-
-
Notifications
You must be signed in to change notification settings - Fork 195
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
Revert #371 #387
Revert #371 #387
Conversation
Doing some minor fixes to this PR, hold on. |
Even with this fix (68bcdd1), the following workflow does not always work for me on https://www.kvb.koeln/app/index.html (scroll down and click "Login", the URL for the database entry is https://kvb.mobilesticket.de):
It seems hard to reproduce now, but it definitely failed the first time I tried it. The autocomplete suggestions were only shown after switching tabs. I then tested it 5 more times, and the credentials were loaded as expected after redetecting the credential fields. However, the 5. step should ideally not be necessary (but maybe that's not in the scope of this PR?). |
@whisdol I'll check those pages if I can reproduce it. It's preferred that everything should work without using the "Redetect credential fields" button. |
Ok, I found a more reliable way to reproduce it:
With this workflow, credentials are never loaded for me. |
@whisdol I could not reproduce the latter one, but the first one does happen (after database unlock). However, after Redetect Credential Fields all works properly. The fields should work right after the unlock though. |
You could try (or merge) #358 because it's related to the issue you are describing. |
With #358 merged into this branch, I cannot reproduce this behavior. After clicking Reconnect, the credentials are loaded correctly on both websites (KVB with frames, DKB without frames). Great, thanks! (Unrelated bug report: the credentials are only displayed in the autocomplete-dialog, not in the extension pop-over after clicking reconnect.) |
@whisdol Great! I'll check the popup behaviour. |
I ended up to a solution that reverts the #371. It just doesn't work properly and in the end it causes more problems than it solves. A much bigger refactor is needed for this, and it makes sense only if it's made after #128 is merged. @droidmonkey Please review this again. Sorry for the inconvenience guys. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with your proposal.
#371 fixed some race conditions, but it's not working properly. Another type of solution is needed. The change needs to be reverted.
Fixes #386.
Fixes #402.