MacBook Pro late 2016 three finger drag issue

Using 13" late 2016 MacBook Pro.

For everybody who is interested:

- Magic Trackpad 2 works just as good as always, no problems there

- Integrated trackpad hardly works with 3 finger drag and generally is less smooth in its operation

I have not tried the new 15" model, but on the 13" one my palms hardly ever touching the trackpad and always rest on the sides next to it while typing.

Patiently waiting for the software update. Fingers crossed for 10.12.2 fixing this.

p.s. Loving the keyboard though. You can type really effortlessly and quiet on it at the same time. Much improved compared to 12 inch MacBook (maybe the way palms are resting also help the typing experience).

I was informed yesterday by apple that the fix most likely will not be in the next update 10.12.2 but on the following to come 10.12.3....

We will need to wait a bit longer I assume...

All MBP with the big trackpad has this issue.

It is mostly related if you have some iron, gold on your hands (like a wedding ring). You can check this yourself by removing the ring(s) and it will work fine.

Probably this happens due the 'palm' detection for typing and disabling the trackpad while doing this.

The only fix would be to disable the 'palm' detection. I did not find a way atm.

No such issue on MacBook Pro 15" 2013, no such issue on MacBook 2016. I do not wear any rings.

It would be really annoing to wait for 10.12.3 release for the fix.

@z3ro1

If you do not wear rings, you do not have the issue. 🙂

But it is a bit annoying and I even think it isn't fixable with a software upgrade. Offering the ability to disable the palm detection is Imo the only solution (sadly).

@ChristopheD: I don't wear a ring and I have this issue. A colleague who is having this issue doesn't wear a ring either. If you try 3-finger drag repeatedly at the middle or left side of the touchpad with no hand resting, palm detection does a false positive on the 3-finger gesture causing the issues described. The resolution that we've tested and found to be repeatably successful is resting your other hand's palm on the touchpad while using the three finger drag with the free hand. This gives the palm detection what it wants - a palm, and doesn't detect false-positive when using the gesture.

It seems to me from your reply that there is yet another issue that when resting your off hand on the trackpad, with a metal ring, causes palm rejection to fail, making the resolution above not work.

@foodbeard:

It seems you are also right. Putting my left hand on the trackpad and dragging with the right hand (3 fingers) works as expected.

But removing my ring also resolve the issue. Both seems to have an impact on the palm detection. Odd.

Because removing my wedding ring is a bit .. heu .. troublesome (read: my wife will ask questions for sure 🙂) I only use the right halve/side of the trackpad. The 3 finger dragging always works on that side.

I am predicting that this new trackpad will cause endofamily conflicts. I have the same issue with and without a ring. No risk for me to argue with the boss 🙂

I am pretty sure I figured out the cause. If you turn off two finger tap for the right menu, and use click on bottom left or right, the three finger drag works correctly 100% of the time. It seems that the OS is having trouble deterring if it is a two or three finger tap when this setting is on.

What if you only disable two finger double tab to zoom?

Actually after trying all day, neither of these two work. So no, it's broken. Really annoying.

No, it does not. When I use my Magic Trackpad 2 attached to my Thunderbolt display (attached to my new MBP) three finger touch and drag works consistently the same as it always has.

However, as soon as I unplug from my Trackpad and Thunderbolt display and just use the new touchpad on my new MBP, it's still very inconsistent.

That is a concern. Let's hope it is a driver problem and not a hardware one. Has anyone had confirmation from Apple that this WILL be fixed in an upgrade?

I did get a confirmation. But probably won't be included in the next update.

I got my new computer a few hours ago and this issue is extremely frustrating. I can' t believe such a basic feature could have been so botched on this new version. Please fix this soon!