Hello ! Same here with Mac OS 14.6.1, Safari 17,6, Bitwarden 2024.08.01 : Press CMD+Shift+L to autofill does not autofill with Username+password, OK with BW extension in the toolbar. Please , update !
Still experiencing this issue: No Autofill using Mac OS Sonoma 14.6.1 (current release) and Safari 17.6 (current release). Just posting to reconfirm and add version numbers.
As mentioned above the Safari beta 18.0 solves this problem but introduces a new one - no passkeys working, so itās not a solution really.
Hello everyone, wanted to chime in and give some updates regarding a resolution for the issues being discussed here.
First I want to mention that the problem happening with Safari isnāt just a Bitwarden issue, though we did re-architect elements of the inline menu that have exacerbated the problem. Safari introduced a significant bug with the release of v17.4 back in March which causes a lockup of the extensionās background script when communicating with content scripts. Extensive details on what Iāve found surrounding the issue can be seen within this Github comment.
That comment also provides some short term suggestions on how to resolve the problem. A long term resolution of this issue will require the release of Safari v18, which will be coming this Fall with the next MacOS update.
Second, the passkeys issue with Safari is related to a separate bugfix that we implemented to resolve some major problems happening within webmail clients that load their content within iframes.
The fix that we implemented delays the injection of our passkeys content script until the HTML of the page has loaded. This fixed the problems we were seeing reported for various webmail clients.
Unfortunately, this delay is also creating the issues with passkeys in Safari that are being expressed in this thread. In effect, the extension is not able to inject the script early enough for Safari to parse and run it before a given website makes a call to the Webauthn passkeys API.
We have a fix going out with the next extension release that should bring the implementation back to parity, while keeping the webmail bugfix in place.
For a more permanent solution, Iām speaking with team members regarding moving forward with Manifest v3 on Safari and Firefox. We have a POC that has been implemented and seems to be working well, but testing is still underway and itās likely that we will release Mv3 for Firefox before Safari for a variety of reasons.
3 Likes
Thanks for the informative update. Much appreciated!
Thanks for your continued work on a great product!
Just clarifying. Iām having the same issues as above, but Iām also not seeing the BW icon appear in the user/pwd fields any longer (even though I still have the option turned on). Are the rest of you experiencing this as well?
For my part, yes: The fully automated auto-fill functionality in Safari has also disappeared along with the āsemi-automatedā keyboard shortcuts no longer working.
Iām far from an expert, but the way I understand Cesarās explanation above, that seems logical to me, since I assume both functionalities are tied to / executed by the same background script.
Yep, back to normal on Safari 18.0. Thanks!
Hi,
+1 here
Since the last update to
- 2024.8.2 (29359) - macOS 14.6.1
- 2024.8.1 (1042) - iOS/iPadOS 17.6.1
the auto-fill function no longer works correctly. When I click on the Bitwarden symbol in the Safari browser or type cmd+shift+L, only the user name is taken over the first time. The password field remains empty.
I have to repeat the process to insert the password. If the login form contains only one password, for example my router, I am offered to copy the password, although it was previously entered independently.
I also often have to insert the vault password for the fingerprint function.
All in all, very annoying. Until then, everything worked perfectly.
Regards
Oliver