Safari stops responding to mouse clicks

How many me-toos until someone notices and fixes this? Aggravating.

I get this too with Safari 17.5 on macos 14.5 using a 24-inch, M1, 2021 iMac. Didn't experience it before macos 14.5. Not seeing it in any other apps. I have to quit and restart Safari when it happens.

I did wonder whether it is related to ad-blocking of cookie notices, but have yet to investigate further. I'm using AdGuard for Safari.

Same on 2021 14" M1 Pro. This started right after upgrading to Sonoma 14.5 and Safari 17.5 . Never had this issue before. Now regular as clockwork. Would be nice if Apple acknowledged this issue.

Yep, same problem here. Sonoma 14.6.1 and Safari 17.6.

I switched to the latest tech preview of Safari and it solved this problem and several others. Safari 17.5 is just a bad release. I don't know why Apple won't acknowledge it, but it is unstable. The Tech Preview has none of these issues for me.

Same on a 2019 MBP 16,1 with latest macOS (Sonoma 14.5) and Safari (17.5 (19618.2.12.11.6)). Does not happen in any other apps.

I can click over to any other app, mouse (MagicMouse) works as expected, click back to Safari, and no bueno. Very repeatable.

Also seems to happen after about 5 minutes of browsing, but that timing is the only thing I cannot reliably repeat.

Thought this problem was due to my older 2017 Intel MBP and OS 13.6.7, but sounds like this happens on newer systems too. Error occurrence is random, sometimes several times a day, sometimes only once every few weeks. Safari disallows input in the URL bar, scrolling locks, and I need to quit, restart, then reopen all tabs from history. It's regular enough to be a real productivity sink, but not an error I can reproduce on demand, so Support is no help here.

It's a shame - Safari has been my go-to browser for security, privacy, and (relative) simplicity. I'll need to move everything over to Firefox I guess.

Not for me, 17.6 still does it on MBP 16 Intel (2019), Sonoma 14.6.1.

For me, downloading the Safari Technical Preview version solved this problem. That implies they have fixed it for an upcoming general release.