Yes, this was intentional for some of the special characters like @. The idea being that the shortcut isn’t shift-2, it’s @. This would means that @ would work regardless of where it is on the keyboard.
Admittedly, maybe it isn’t the right way for things to work, and we should more closely follow the web API standards for this. We’ll discuss more internally