-
Notifications
You must be signed in to change notification settings - Fork 53
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
Not copying to clipboard? #194
Comments
Odd... permissions shouldn't required these days @polm. I made a few commits to try and fix this. Could you:
Give it a try to see if the bug still persists and report your findings back here? |
Any update @polm ? |
Sorry for the delay. I tried the version from master and the copy function works there and it does not work in the version I currently have installed. My current version is 0.9.4 ID Also, in the currently installed version and the version from master, pushing Enter to fill password fields doesn't work, nothing happens. The fill button itself still works if clicked. |
Anything else I can do to help debug this? |
I actually fixed this weeks ago, @GitTom hasn't had the time to update the official version yet. So @GitTom would you either be able to migrate your (.org) extension to the PasswordMaker group on the Chrome Web Store so I can update it using the 3Dot menu at the top of your extension entry as I have done or update it for your users? Ideally you migrate it to the publisher group that @miquelfire made so I can handle it atm. |
The group invitation has expired - sorry about that. Can you @miquelfire please invite me again. |
Resent the invite |
Got it. I followed up in the other thread. |
Should be updated now @polm. |
Thanks! I confirmed it's working again. |
I recently noticed that the "copy" button doesn't seem to do anything. It's like the extension doesn't have permission to access the clipboard, though I don't get a warning or anything. Is this expected, or is there something I can do to debug it further?
The "fill" button works as usual.
The text was updated successfully, but these errors were encountered: