The issue I’m having is that the “Disable OS Keyboard Shortcuts” doesn’t seem to be working. I’ve removed World of Warcraft from System Settings → Accessibility and readded it. I have several keybinds to CMD+Q, which, yes, I know will quit the app. But before TWW patch, these keybinds worked without an issue.
Edit: I remember when selecting “Disable OS Keyboard Shortcuts” pre-TWW patch, there was a popup saying that I had to give World of Warcraft Accessibility access. I removed World of Warcraft from Accessibility, started the game up, checked the “Disable OS Keyboard Shortcuts” box and did not get that popup.
I’m using a Razor Naga Mouse with a Razor Black Widow Keyboard, the computer is a M3 MacBook Pro and I have it connected to external keyboard mouse and monitor. I’ve had this set up for awhile. Previously I had this same issue about a year ago but folks on here said to input this terminal string and it fixed it. Seems like it fixed it for everyone. But when I tried it again it no longer works.
razer naga x mouse, the 12 button pad bound to keyboard buttons rather than numbers. M1 mac mini. standard us keyboard. i’ve had the same set up since the end of BFA with no issues until the last few weeks of beta, and now live with prepatch.
The above worked for years now and on this patch it seems to be ineffective? I ran cat defaults read to check com.blizzard.worldofwarcraft still has disable-expose-fix set
So its still defined, but not behaving how we would expect?
MBP 16 M3 Max, Steelseries Rival 500, enUS keyboard (Corsair K100). Everything worked fine before 11.0 although I did notice Shift modified mouse buttons not working on the beta. I have several spells mapped to stuff like F12/Shift-F12 with those keys mapped to a button on the mouse. F12 works fine, Shift-F12 passes F12 again.
On the keyboard, everything works fine (i.e., Shift-F12 casts the Shift-F12 spell. It’s only with the mouse.
Issues here with mouseover macro’s on mouse buttons, using a G502 with Steermouse. Having this in both latest Sonoma as in the beta of Sequoia (US keyboard).
So I went to Best Buy and got a Razer Naga. I can now reproduce the issue. It looks like the fake keyboard events the mouse is generating are claiming that there are no modifier keys being held (even though the physical keyboard modifier key is being held down).
I understand why this worked in the old code and why it doesn’t work in the new code. Handing this case in the new code will take some thinking, but I imagine we can make a fix fairly soon.
M3 MBP
macOS Sonoma 14.5
enUS keyboard layout
Naga Pro (RZ01-0342) and I do NOT have the Razer software installed
use the 12 button side that maps to 1,2,3,4,5,6,7,8,9,0,-,= as default
use Control and Shift as modifiers
I can hit Shift/Control + number on my keyboard and it is recognized fine in retail. Hitting Shift/Control + number button on my MMO mouse is not recognized. Hitting just the number button on my mouse alone is recognized.
Fixed I’ve tried:
System Settings > Privacy & Security > Accessibility > toggle on allowing World of Warcraft
System Settings > Privacy & Security > Input Monitoring > Added World of Warcraft and verified its toggled on
WoW > Options > System > Keyboard Options > Disable OS Keyboard Shortcuts is toggled OFF
In Terminal: (Note, this did work previously when I had issues with Shift when I first swapped to playing WoW on a Mac a year+ ago)
defaults write com.blizzard.worldofwarcraft disable-expose-fix -bool YES
A third party software to map your mouse as though they are keyboard presses has been suggested but I refuse to install that. The game should be fixed, and sounds like it was fixed in Beta. Appreciate you all looking into it even though us Mac players make up a small portion of the community. It was working fine before 11.0. karabiner-elements is the name of it
As another update, it appears these mice needed defaults write com.blizzard.worldofwarcraft disable-expose-fix -bool YES
to work in the old client. The code using disable-expose-fix is not present in the new client currently. I’ll work on re-adding that in an 11.0.0 hotfix.
Longer term, I’ll work on adding this option to the UI in a future patch (or figure out a way to not need this config option).
So, I was having the same problem… Installed karabiner and rebooted my MAC and its working now.
I have a razer naga trinity and MBP M1 Max 32GB with MacOS Sequoia Beta v3 (I know beta is unsupported). Posting here as this might solve for some other people.
Just adding in here, I use a third party software called SteerMouse and updating it and ensuring my binds were correct (Naga to the numbers) fixed the issue for me.
Now if I could just get the screen resolution situation resoved I’d be set.