chrmyr wrote:
"I contacted Apple today again to get an update on this. Short story: There is no update. A bug report has been filed and that's it. Priority is up to Apple. Additionally, Apple is super silent about what priority is."
Once again, I offer this thought:
This may have been an INTENTIONAL change by Apple's software designers.
Although, I have no idea as to WHY they would do so.
Perhaps to bring something closer to the way iOS works?
(I have NO real experience with iOS, I've never owned an iPhone or iPad)
I just want to come back to this. As to my knowledge, there was one major change for the pointer behavior which is in Accessibility "Ignore Trackpad if a mouse is connected" (see Accessbility > Cursor / Pointer).
"Intentional" for me means in this context a change with effects that are considered to be the purpose and aimed for.
I do not think it is intentional and there is one simple explanation for this:
The behavior is still as it was in 14.0 when changing secondary-click to trigger when "two-finger click" (this is also the only known workaround at the moment).
Either the change was intentional and this specific (just named two-finger click) secondary-click behavior was forgotten to be changed or it is a bug. However, after comparing it with an older external Trackpad (A1339), the behavior still works under macOS 15.2 when using the external (older) trackpad: no bug with the older trackpad. Someone mentioned trying it out with the newer external trackpad and the same issue occurs.
So we need to drill down what the issue really is. My list as of now would be
- macOS General Cursor behavior
- macOS Secondary-Click .plist Settings
- macOS .kext Driver for AppleMultiTouchTrackpad
- Interference with the third-party app receiving the gesture
Of course we are never sure as we do not have enough insights.
4. Interference with the third party receiving the gesture
After trying different apps that rely on 3D-controlling/visual controlling with an XYZ-perspective they all behave in the same (false) way. Even apps that are 20 years old and have not changed how their inputs work see this issue. So the issue exists outside the third-party app
2. macOS Secondary-Click .plist Settings
Multiple people here have tried various setting combinations, even settings that cannot be done via the UI in the settings app. None helped to solve the issue. Just changing the secondary-click trigger to "Two-finger click" solves it. Of course it could a combination that was not tried, but my guess is: the chances are pretty low that this is solvable using the settings how the secondary-click works for lower-right / lower-left corner. The .plist settings is therefore also not likely to be the root here.
1. macOS General Cursor behavior
This is what you are refering to
@Fishrrman if I understand you correctly (please also see Nr. 3, too). As mentioned before, it could be as we cannot be certain 100% but from my perspective unlikely since this occurs only for secondary-click lower-left and lower-right corner. From my opinion, there is no logical connection why this behavior should only be observable for lower-left and lower-right corner and was not changed for two-finger click aswell. There could be an intentional change somewhere else in the system for the Cursor behavior so that this issue is a side effect. But this would likely mean that external devices like magic mouse or external trackpads would reproduce the issue aswell. This is not the case.
3. macOS .kext Driver for AppleMultiTouchTrackpad
When comparing the .kext Driver we can see actual changes in the version number. Could be that there is always a new build when a new macOS is released but after talking to the Apple Support they are also certain that some changes happened. The changes here were certainly done on purpose.
The main point I want to close my list with is that I am sure that this change was done on purpose/intentional but not with this effect in mind.
My current perspective is also that everyone on Apple's side is considering this as a bug. However, no resource was assigned or the bug is not resolved yet.
@everyone: Therefore, please see my post from yesterday to contact Apple Support. They likely do their priority based on impact. That means, the more impact (scale) an issue has, the more likely it is resolved quickly. This means multiple reports need to fly in from all across the globe on a larger scale.