Patrick Harböck

Hi @torfmaster, thanks for raising this issue. Is it correct to assume, that gopass on your terminal works without issue? Did you follow the steps to setup the gopass jsonapi...

Also maybe try to restart your gpg-agent, it seems to help sometimes: https://github.com/gopasspw/gopassbridge/issues/152#issuecomment-658337911

@yanchenko-igor As far as I understand your issue, I cannot reproduce it on Chrome 74 with gopassbridge 0.5.1 on Mac with pinentry-mac because the gopassbridge menu stays open after entering...

Having a separate configuration option to turn off the persistent detail view is probably the simplest and realistic solution to your problem that can be implemented easily.

Hey @rounakdatta, Sounds like a good idea. Personally I use the gopass CLI for this, but a simple integration of "gopass generate" would be a nice addition to the browser...

Thanks @liljenstolpe for pointing our this inconsistency. While I agree that gopass and gopassbridge should use the same default settings, there is also the **Default folder for new credentials** setting...

@liljenstolpe In the extension options (In Chrome right-click the gopassbridge icon and click "Options") There is **Default folder for new credentials**, which can be used to also select different mounts...

Thank you for the suggestion. Sounds like a good improvement. With the latest changes this issue belongs now to the [gopass-jsonapi repository](https://github.com/gopasspw/gopass-jsonapi). The code where we handle these browsers can...

@Spass1966 Yes, TOTP codes should be shown in the detail view of a gopass entry which has the "totp" attribute set ([click this icon to expand it](https://github.com/gopasspw/gopassbridge/blob/master/web-extension/icons/si-glyph-arrow-thick-thin-down.svg)). The code should...

@Scrumplex Thank you for this deep investigation. I can imagine that we could just remove the `background: white` on `body` and `.login`, at least for my Chrome browser they don't...