Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
So yesterday morning I updated my cheap intel “stop gap” MBP, tested and could not believe my eyes, or track pad….. issue fixed!!!! Yesterday evening I went to the local Apple Store and tested on both the M1 and M2 display units with no issues! Grabbed a 14” M2 Max and just finished setting up, zero track pad issues.
Just updated to latest Ventura on both the intel and M2, tap to click still behaving on both.
 
13.3 works fine 16“MacBook Pro m1pro bug fixed

"You need to use an external keyboard to fix the issue. The bug has been fixed when using an external keyboard, but it still exists with the built-in keyboard. I'm using a Magic Keyboard and a software called Karabiner to disable the built-in keyboard."
 
Last edited:
Can u tell us more?
"You need to use an external keyboard to fix the issue. The bug has been fixed when using an external keyboard, but it still exists with the built-in keyboard. I'm using a Magic Keyboard and a software called Karabiner to disable the built-in keyboard." m1pro macbook 16”
 
"You need to use an external keyboard to fix the issue. The bug has been fixed when using an external keyboard, but it still exists with the built-in keyboard. I'm using a Magic Keyboard and a software called Karabiner to disable the built-in keyboard." m1pro macbook 16”
So, without a external keyboard the tap to click issue on the edge of the trackpad is sill in this beta, right?
 
So, without a external keyboard the tap to click issue on the edge of the trackpad is sill in this beta, right?
That's correct, it's the same for me. The issue disappears when using an external keyboard in combination with the trackpad. Only one click is needed."
 
  • Sad
Reactions: racostaf
Any news on the issue? For me it was gone for a while, then back, i think with 13.2.1. But now I feel that it has gone away with 13.3. :)
 
  • Like
Reactions: tom1244
A little heartbroken over this issue - just out of the 14 days return period and didn't have time to dig deeper until now.

I use CMD+tap thousands of times a day in Chrome and VS Code and it's certainly noticeable when you keep having your flow interrupted several times per minute

Finding threads all over the web that suggest the issue is both widespread, and being largely ignored by Apple. After coming from a MacBook Pro with the keyboard issue, where I would have to take it in at least once a year to have the keyboard (and entire chassis) replaced, I'm more than a little mad about the prospect of another hardware issue. Definitely not happy about the idea of surrendering my laptop and the work on it for a few days while Apple investigate another widespread hardware problem

I'm also hoping that it's a software issue that can be fixed with an update. The fact it almost always works on the third tap suggests so, unless we're all getting so frustrated by the third tap that we force an actual click instead of a tap

The other option I'm considering is making a fuss in store and returning it. I need the power of the M2 Max for compiling C++ programs, but maybe I'm better off with a different laptop/brand, and then start offloading my compute into the cloud.
 
  • Like
Reactions: AlumaMac
A little heartbroken over this issue - just out of the 14 days return period and didn't have time to dig deeper until now.

I use CMD+tap thousands of times a day in Chrome and VS Code and it's certainly noticeable when you keep having your flow interrupted several times per minute

Finding threads all over the web that suggest the issue is both widespread, and being largely ignored by Apple. After coming from a MacBook Pro with the keyboard issue, where I would have to take it in at least once a year to have the keyboard (and entire chassis) replaced, I'm more than a little mad about the prospect of another hardware issue. Definitely not happy about the idea of surrendering my laptop and the work on it for a few days while Apple investigate another widespread hardware problem

I'm also hoping that it's a software issue that can be fixed with an update. The fact it almost always works on the third tap suggests so, unless we're all getting so frustrated by the third tap that we force an actual click instead of a tap

The other option I'm considering is making a fuss in store and returning it. I need the power of the M2 Max for compiling C++ programs, but maybe I'm better off with a different laptop/brand, and then start offloading my compute into the cloud.
So. You have the last update and see the issue ?
 
So. You have the last update and see the issue ?

Yes, I just installed 13.3 this morning and the issue is still present.

I've tried a few different things like turning off all trackpad gestures and testing with and without an external display connected

I also seem to remember some of the earlier macbooks would reserve a small strip on the right hand side of the trackpad for scrolling. Since I can reproduce this issue best when using that portion of the trackpad, does anyone know if there is another setting somewhere for this old scroll behaviour? Would be great to be able to turn it off and test again
 
A little heartbroken over this issue - just out of the 14 days return period and didn't have time to dig deeper until now.

I use CMD+tap thousands of times a day in Chrome and VS Code and it's certainly noticeable when you keep having your flow interrupted several times per minute

Finding threads all over the web that suggest the issue is both widespread, and being largely ignored by Apple. After coming from a MacBook Pro with the keyboard issue, where I would have to take it in at least once a year to have the keyboard (and entire chassis) replaced, I'm more than a little mad about the prospect of another hardware issue. Definitely not happy about the idea of surrendering my laptop and the work on it for a few days while Apple investigate another widespread hardware problem

I'm also hoping that it's a software issue that can be fixed with an update. The fact it almost always works on the third tap suggests so, unless we're all getting so frustrated by the third tap that we force an actual click instead of a tap

The other option I'm considering is making a fuss in store and returning it. I need the power of the M2 Max for compiling C++ programs, but maybe I'm better off with a different laptop/brand, and then start offloading my compute into the cloud.
Do you have m2 pro ?
 
It's more than 2 years since the introduction of this bug in Monterey. Well done, Apple! I haven't seen such a sh*t in a long time! The only stable version is Big Sur (< M1 Pro).
 
  • Like
Reactions: lkozierowski
It's more than 2 years since the introduction of this bug in Monterey. Well done, Apple! I haven't seen such a sh*t in a long time! The only stable version is Big Sur (< M1 Pro).
How bad is it working for you? For me it misses taps occasionally.
 
I returned MBP 14 because of this bug and now I'm on Intel-based MBP 2020 with Big Sur. I'm waiting for this problem to be fixed. Working with that bug for a few minutes driving me nuts (mostly open new tab in browser, text editors).
 
I returned MBP 14 because of this bug and now I'm on Intel-based MBP 2020 with Big Sur. I'm waiting for this problem to be fixed. Working with that bug for a few minutes driving me nuts (mostly open new tab in browser, text editors).
I hear you!

Unfortunately, I'm swamped with work and can't troubleshoot right now... I'll just let my seething anger fester for the time being.

As an alternative, I'm thinking of turning off tap to click entirely, meaning I'll have to painfully unstitch over a decade of deeply ingrained muscle memory.
 
What can we do? I was in 3 apple store and they said than is a normal behavior... is nothing documents that indicate that should works on the edges...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.