I don't get on Reddit so often, if you do want to reach out, my email is listed in the only open Github issue (#15) in the above linked repo.Ĭheck out Vivaldi and Brave. My source linked above might be of help to figure out messaging methodology. I am in no way an expert with Apple, Swift or Xcode, but I would gladly offer my help to figure out a plan for porting Bitwarden, if desired. The biggest challenge for me was figuring out how to easily manage messaging between the injected script, the view controller and the popover javascript - once I figured that out (which was an adventure due to the aforementioned documentation issues), I realized I could write 90%+ of my code in javascript. I haven't used Bitwarden but from if you're doing everything from the popover, this could probably be done using mostly Javascript. It was/is a pain, but more manageable than I thought it would be. I recently ported one of my extensions from the "legacy" format. If someone who is knowledgeable with writing Safari Extension Apps, or even better, making an existing WebExtension somehow work with Apple's new API, wants to provide some consulting on how we can bring Bitwarden back to Safari, please let me know. For someone who is not well versed in the Apple development ecosystem, Apple's documentation and other community resources on writing Safari Extension Apps (the new way) is pretty sparse.Maintaining a completely different browser extension codebase for that many users isn't feasible. Safari currently accounts for Apple's new way requires re-writing the extension interface and backend using native Swift/Objective-C. All other browsers use a standard way of writing extensions (called WebExtensions) with web technologies like HTML, JavaScript, CSS. As far as I understand, this means that we cannot use our existing browser extension code any longer. Apple has introduced a completely new way of writing extensions for Safari.
I am not sure we will be able to continue supporting Safari in the near future.
0 kommentar(er)
