How can I disable Snap intercepting all CMD keypress combinations on macOS

Help with Snap! Snap! Editor
1

(This is a template, feel free to delete it.)

What's problem you are encountering?

When I open Snap in Safari (this doesn't happen in Chrome) I cannot use CMD anymore to cycle through all the open macOS windows.

What have you tried that didn't work?

CMD+Tab/ShiftTab doesn't allow me to move to the next/previous open window in macOS.

I like a lot having shortcut combinations in Snap. So, can I disable Snap intercepting just specific combinations? Or can CMD be (optionally?) moved to CTRL in macOS?

2

I use macOS nothing happens to me.

3

Can you switch to other open windows by using CMD+Tab?

4

well it acts like I can but it won't do anything when I try.
I also use safari.

5

Weird, that should be standard macOS behaviour Manage windows on Mac - Apple Support

6

In Chrome, ⌘ does the usual browser thing and ^ does the Snap! thing. Not in Firefox either. Much as I hate to say anything nice about Google...

7

Why do you hate google so much?

8

I guess it's because multi-billion-dollar corporations have a lot of negative connotations

9

Because they invented the modern no-privacy era. Go read Shoshana Zuboff | The Age of Surveillance Capitalism.

10

Oof. Even the first few paragraphs tells the story.

11

Oh, there's a lot more than that to the story! Read the book...

12

So, Google, Facebook, Etc. Can use your private info for money?

13

Oh yes! How did you think they got so rich? They make a point of how virtuous they are because they don't directly sell your info to other companies; they just use it to target advertising to you that they predict you'll click on. But they have the information, and (sometimes) they respond to police subpoenas.

14

Can this behavior -⌘ doing the usual browser thing and ^ doing the Snap*!* thing- be implemented so that it works with Safari too?

15

I think we do the best we can, given what the browser tells us.

It's funny, you'd have thought a priori that Safari, written specifically for MacOS, would do the best job of keeping command and control separate. But no.

16

I thought that CTRL and CMD were firing different key codes, as in https://codepen.io/chriscoyier/pen/mPgoYJ?

17

Yes, but that doesn't mean it's what the browser tells us. If we were getting raw key codes, it'd already work the same on all browsers. :~)

18

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.