-
Notifications
You must be signed in to change notification settings - Fork 973
bitwarden issues while testing #10202
Comments
Updated with a few more testing on my windows laptop. One critical issue discovered with autofill. |
@kspearrin Thank you! We'll take a look asap. |
@jonathansampson Added 2 new issues for macbook, see 4 and 5 above. 5 is a high priority. |
@kspearrin Working on resolving #10140 right now. |
@kspearrin would you mind checking a report from an user here? https://community.brave.com/t/bitwarden-extension/5403?u=suguru thanks! |
@luixxiul we did not intentionally release bitwarden and we have known issues @kspearrin I responded to the user and let them know that we're working to fix the issues on our (Brave) side 😄 Apologies for any uptick in support |
@kspearrin I wasn't able to reproduce Vault locks while popup is still open. Could you record a small GIF or video showing the precise steps to follow? |
Any idea if 3 and 5 will make it into the v0.19 release? Those are really the only 2 big ones that I can find while using the beta. |
Testing brave v0.19 now with bitwarden. Issues 1, 2, 3, 4, and 5 from above are still happening. |
The extension has now been updated to latest (1.25.3) in Brave thanks to me and @jonathansampson doing some testing and all issues 1, 2, 3, 4 and 5 are still reproducible when using brave 0.21.24 and bitwarden 1.25.3! I added one more issue to to the issue at top that I found while testing 🙂 |
We haven't updated our extension support in Muon for a while- but we will get proper extension support when we move over to brave-core. @kspearrin thanks for all the work you did with us in the past as we did try to add those missing APIs 😄 It'll be nice to have bitwarden working properly once we make the move over |
At the request of @jonathansampson , here are a list of known issues while testing bitwarden v1.14.2 with Brave 0.18.14. This list is a WIP and will be amended as issues are found.
#9437
Macbook
1. Cannot expand vault to full screen - Low priority
2. Default browser_action keyboard shortcut does not work - Low priority
command + shift + y
to open bitwarden.Popup should open with hotkey as defined in https://developer.chrome.com/extensions/commands
See bitwarden implementation here: https://github.com/bitwarden/browser/blob/master/src/manifest.json#L74
Chrome docs state:
3. Vault locks while popup is still open - High Priotity
Locking is not suppose to occur while the popup is open. This is prevented by checking for the popup to be open with
chrome.extension.getViews({ type: 'popup' })
. See here: https://github.com/bitwarden/browser/blob/master/src/services/lockService.js#L25I'm guessing that this API is not implemented on Brave.
4. Dev tools content scripts doesn't show i18n extension name - Priority low
Dev tools is showing the i18n variable name instead of the
messages.json
value.I know there was an issue in the extension listing page a while back that was related to this. Saw it while debugging so thought I would report it.
5. Notification bar doesn't work due to CSP violation from content script injection - Priority medium/high
bitwarden shows a notification bar to assist with adding new sites to your vault whenever you log in manually and the extension detects the credentials don't already exist in your vault. This is failing due to a CSP violation when the content script tries to inject an iframe into the host page.
bitwarden source: https://github.com/bitwarden/browser/blob/master/src/content/notificationBar.js#L185
6. Wrong logo size makes the icon look blurry and low res - Priority low
This is bitwarden i Brave compared to chrome:
Brave are using "Icon19":
While chrome are using "Icon38":
The text was updated successfully, but these errors were encountered: