Safari converts first 2 characters while invisibly typing password

Question

Level 2

150 points

Safari converts first 2 characters while invisibly typing password

This bug occurred on Safari 18, macOS 15. On many/most login forms (but apparently not all, like Gmail), when the password is being typed when it is not visible (showing as •), it seems the first 2 characters get converted to a bullet and a whitespace ("• " without quotes), preventing me from logging in.

This can be inferred by choosing to show the password after typing it. For example, in the login form at Casting Networks, I tried to type "abc123" (a fake password for demo purposes), but when I select to show what I had typed, it shows "• c123". So "ab" got converted to the aforementioned characters.

The workaround is to type the password when visible, or, if visibility is not an option on the form, type elsewhere and copy/paste. Or use another browser. But this needs to be fixed ASAP.

I reported this to Apple and am wondering if anyone knows a better resolution/workaround until there's an official fix.

MacBook Air 13″

Posted on Oct 2, 2024 7:07 PM

Reply

Answer 1

Connor Hawke Author

Level 2

150 points

Oct 11, 2024 10:17 AM in response to Connor Hawke

Still happening as of Sequioa 15.0.1, Safari 18.0.1. How is this critical issue not fixed yet? Did I get a faulty Safari/OS? Happens with the on-screen keyboard too. Only on Safari, not other browsers. Also, another issue with Safari: it seems to force itself over TextEdit. Here's a screen recording of the password issue:

https://youtu.be/aNpxrPreS0Q

Reply

Answer 2

Connor Hawke Author

Level 2

150 points

Oct 17, 2024 9:11 AM in response to Connor Hawke

Bingo... found the issue (for the password bug). It only happens when "Correct spelling automatically" is on (in System Settings > Keyboard > Text Input > Input Sources > Edit). Once I disabled that, no more issue with the first two characters in a hidden password being replaced with a bullet and whitespace.

Definitely a bug that needs fixing but at least there's a workaround for now. I always disable autocorrect on all my devices anyway, guess I forgot to do it with my new MacBook.

As for Safari forcing itself over TextEdit, if anyone finds a solution, feel free to share.

Reply