I discovered a solution to CMD + tap (and SHIFT + tap) being missed:
On the built-in trackpad, there's a central rectangle area a bit smaller than the size of the smaller trackpads older macbooks had before they started putting these massive ones in. The 3-taps required to get CMD + tap to register can be avoided by clicking in this central region instead of more toward the edges. Also note that the first tap must be in this central region. If you first click more toward the outside and it misses it, the trackpad will also reject a followup central tap.
Before that, CMD + tap routinely took 3 taps to multi-select files in Finder. And of course, if I forget and do CMD + tap more toward the edges, 3 it is again. So this required a bit of retraining for me to use the smaller central rectangle region for tap to click, but it's comfortable now.
Now I only use the larger area outside that smaller central rectangle area for continuing long drags. Some might say this is more of a workaround than a solution, but it saved my sanity.
It's almost as if the driver that rejects trackpad input while a key is pressed is working off the dimensions of the older model macbooks' trackpad dimensions.
All this is on:
- 2019 16" MacBook Pro
- built-in trackpad
- Catalina, Big Sur, and Monterey 12.1
Peter
I have the same problem. I just returned my brand new MacbookPro today.
I am worried that as of 2022/04/17, seventeen hundred people are experiencing the same issue and there is no official reply from Apple. In one of the posts from other people, one customer went to the Apple Store and was able to reproduce the issue in every laptop. In another post, a customer ordered a replacement unit and the new laptop had the same defect. This is a YouTube video that demonstrates the problem: https://youtu.be/l4daQQeuzNw
To me, it feels unfair to pay for a laptop where the Track-Pad is not working as intended.
There are similar reports dating back to 2020, and there is still no answer from Apple:
https://discussions.apple.com/thread/253382140https://discussions.apple.com/thread/252211114I wonder whether Apple is able to fix the problem.