Can't type: This site's hotkeys are overriding my keyboard layout

edit

Thank you for your reply.

1. Yes, that is true. 2. Google Chrome. 3. Not necessary since the defects are in this site's code, not the browser's. 4. On Windows mainly. 5. Correct me if I'm wrong – input methods do not handle keys entered in text boxes, they are an earlier layer. They are reasonably responsible for the events received by the text boxes.

This site has most likely decided to hardcore arbitrary interpretations of key combos = defective by design, in the same way a game is in which you cannot customize the controls. Unplayable unless you figure out the dev's keyboard layout.

I have never seen a website that allows you to modify the editor keystrokes. The site's code is not the problem. It's something with your operating system's input method and how the keystrokes get passed to the browser. If you can reproduce this issue with Firefox on Fedora, you would have a case. But given that no one else has complained about this, that's unlikely.

@samuel-sieb Thanks for the info and the suggestion. I will try it out if given an opportunity, and update the question accordingly.

I think I understand what you mean now. You're saying that the input method should reasonably consume the appropriate keys/events, but fails to, which causes the hotkeys to trigger unexpectedly.

Right, the operating system should be taking those keystrokes and passing on the resulting character, but somehow the browser is seeing the raw keycodes. It's also possible that Chrome is reading the input the wrong way so it's getting raw codes instead of the processed ones.

To put it another way, there is no way you could expect the website to know what keyboard layout you are using and handle raw keycodes appropriately.

Thank you for your reply. I am not looking for a solution. I have no intention of doing any kinds of inconvenient workarounds for something as trivial as text input ...on a site that's mainly about inputting text. I'm just going to avoid using the site. I merely posted the problem so that it would get fixed. If it doesn't get fixed (which seems to be the case), then I will continue to stay away. I'll be fine -- 99.999% of the web doesn't have these problems.

We don't control the code running the site; it runs on Askbot, and if you want to complain about the way it handles some keystrokes, take your complaint to them.

"Take your complaint to them" My interests lie with Ask Fedora, not Askbot. But, of course, I suppose that your view would be a convenient way to look at things for whoever runs Ask Fedora; Nothing has to do with Ask Fedora. If I close my eyes really hard it's almost as if this site doesn't even lose users because of Askbot's code, so what possible incentive could Ask Fedora have to report its problems to Askbot. All is well.

If there were large numbers of complaints, you can bet that the Fedora Project would be complaining to Askbot. As it is, you seem to be the only person affected, so it's best if you report the issue because only you can give them the information they need. Unless, of course, you're more interested in complaining than in getting it fixed.

I don't see the need to imply I'm "interested in complaining" just because I report bugs. It's not unheard of to let people know about software defects. If it weren't clear already, no, I'm not happy with how this works and I didn't make it up because I want to complain. The problem exists, and that's a fact. I'm not heavily invested in this site, hence I'm not motivated to go out of my way to look up some obscure bug tracker. The fact that you call bug reporting "complaining" tells me you've mistaken my lack of investment for something else. If no one else is invested either, then that's fine