68

Although the extension behaves better in new releases, there situations (I cannot determine the conditions) in which is fails and it is seems a common issue to other extensions

    The Chrome and Firefox extensions seem to be working correctly now with the latest Orion version (0.99.126.2-beta). However, it still renders in a way that makes most of the UI invisible. See screenshot, this is the Firefox extension but the same happens to the Chrome extension. Not sure if this something that can be fixed by the Orion devs or should be fixed by the developer of the extension.

      10 days later

      Related to this one, it seems that this extension is not working as expected, but I'm not sure if this is related only to my machine or if this is a general issue. The issue I'm experiencing (apart from the above mentioned) is that when I search for entries in my Strongbox password DB, it doesn't find any entries even when it should find them. The same is true about the small box that shows up on a login form on the page. This box normally shows entries from my password DB that match the website url, but in Orion it is always empty. Looking at the website's (not the extension's) devtools, it seems that whenever the small box shows up, an error is added to the devtools console:

      Failed to load resource: Nie można ukończyć tej operacji. (Błąd Orion.SchemeHandlerError 2.)
      My browser language is polish, and so the translation of the above error is:
      Failed to load resource: Can't finish this operation. (Error Orion.SchemeHandlerError 2.)

      Hope this helps with some debugging 🙂

        2 months later

        This is still an issue in Version 0.99.126.4.1-beta (WebKit 618.1.2). I think it's actually a more generalized issue since it happens to other extensions sometimes as well, I've seen it happen to "cookie autodelete".

        In addition it the Strongbox autofill popup is unreliable with both the chrome and firefox extensions. Sometimes it shows up immediately when clicking a login or password field. Sometimes it won't show up at all. Sometimes it appears once then fails to appear again if closed. This is especially common if the database is locked and you use the popup's prompt to unlock the database. Once the database is unlocked the popup should show again immediately with possible autofill entries but most of the time it does not and it's usually not possible to get it to show again (both firefox and chrome extensions).

          I noticed this is tagged as "done" @Vlad could you please reopen it?

            Hey, Ican confirm that I'm also experiencing those issues. I'm also on version 0.99.126.4.1-beta (WebKit 618.1.2). Exactly as described by Evelant. I would also assume that this issue is related to Orion, rather than the extension itself, since it works fine in other browsers.

              Merged 7 posts from Strongbox UI issue (expand popup).
                a month later

                balph

                I think that is a problem in Orion itself. I'm having similar problems at rendering with ublock extension as well

                    4 months later

                    In July of 2024, why is this STILL an issue @Orion?????? This has been happening in more than half the websites I use and does not happen on Chrome or Safari. Why haven't you fixed this when the OP started this thread TWO YEARS ago. Clearly, it's a problem with Orion.

                    • dino replied to this.

                      kelleychambers can you please share steps to reproduce. and some other informations as well

                      1. Are you using firefox or chrome extension?
                      2. What Orion version you are using?
                      3. what macOS version you are using?

                          dino I'm not now. I dumped the browser. Went back to Safari. Thanks for checking in.

                          Steps to reproduce? This has been addressed over and over this thread. My path is no different.
                          I was using the latest stable version of Orion as and, at the time, the latest macOS beta for Sonoma. I'm now on the public beta for Sequoia.

                          I can update my original post by telling you that this is actually an issue now with Safari, too. After quite a bit of research, Bitwarden is aware of the "defect" and is fixing it in the next version. Whether or not it will hold is anyone's guess as this has been a trend with them for the last two years.

                          Lastly, I've dumped Bitwarden and gone to the new keychain that Safari uses. Much better. Yeah, I miss my extensions but things seem to be getting better on that front, too. Just sick to death of things that are supposed to be so great turning out to be turds when I use them.

                              2 months later

                              I just started using Orion and I wanted to chime in saying that I'm getting the same issue with autofill not working. Unable to see the autofill button next to username/password fields like on FireFox/Chrome and unable to autofill the credentials through the extension like OP's initial post.

                              1. I've tried both the Firefox and the Chrome extension, same issue.
                              2. Version 0.99.128.2.1-beta (WebKit 619.1.11.111.2)
                              3. Sequoia

                              This is listed as a popular extension in the Extensions page and it's been over 2 years since this post, I am honestly shocked that this is still an issue.

                              Install the Bitwarden (from Chrome/Firefox store) extension, then login.

                              This seems to happen after I added lots of passwords, it previously worked fine.

                              Orion version 0.99.127.2-rc, Monterey/Sonoma

                              UPDATE: The version in "Popular Extensions" works normally, but not the latest (both Chrome/Firefox store)

                                Works for me on 0.99.127.1-beta. It might happen if you just logged in and it hasn't synched everything yet.

                                I got the same problem. The real issue might be the auto-update feature that you toggled. The version in popular extension pannel works fine, while the latest version of bitwarden just won't.

                                I am happy to report some of the bugs I encountered when bitwarden is auto-updated if needed.

                                  I had the same issue with the empty vault after updating the Bitwarden extension to the latest version, but restarting the browser seemed to fix it (in my case).

                                  Update: The version in "Popular Extensions" works normally, but not the latest (both Chrome/Firefox store)