You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 10, 2023. It is now read-only.
Sure! I will try to port the newest version of the browser extension soon. Currently working on my Bachelor's thesis so won't have much time to work on this. But I'll do my best 😄
I worked on this for a few days now and I am afraid I have to conclude that this will not be possible. Starting from version 1.49.0 with commit bitwarden/browser a2540ab , the Bitwarden browser extension uses the new Safari Web Exentsions API. This is a big leap forward for the extension itself and means that the Bitwarden team does not have to carry around extra code for the Safari extension which previously worked differently as compared to the Chrome/Firefox version. At the same time, this introduces breaking changes in the way the JavaScript code interacts with the application. Previously a user content controller was responsible for messages send by JavaScript to the application/system
Now, this is done with the new SafariWebExtensionHandler introduced by the Bitwarden team. For now, I was unable to attach this extension handler outside of a Safari extension in a normal macOS trap application and thereby unable to intersect messages send by the JavaScript components of the extension.
Maybe someone with more expertise in this area can come along and help me out implementing the message handler. The current state of the application only displays a spinning loader as some JavaScript components fail to initialise correctly.
Any chance you can update this please to the new 1.52.1 version of Bitwarden?
The text was updated successfully, but these errors were encountered: