Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Keydown Event does not work for Control, Shift and Alt keys?

  • 4 Antworten
  • 1 hat dieses Problem
  • 7 Aufrufe
  • Letzte Antwort von Einhornyordle

more options

If you execute the following code in the browser's console

onkeydown = function(e){console.log(e);};

it should log every keypress to the console window, however, the event doesn't seem to fire when I press Control, Alt or Shift (by themselves, keycombos like Shift + W work). Trying the same in Edge for example works for every key, including the three mentioned. Am I doing something wrong or is this a bug of firefox? I should also mention that I'm using the developer edition of firefox.

If you execute the following code in the browser's console onkeydown = function(e){console.log(e);}; it should log every keypress to the console window, however, the event doesn't seem to fire when I press Control, Alt or Shift (by themselves, keycombos like Shift + W work). Trying the same in Edge for example works for every key, including the three mentioned. Am I doing something wrong or is this a bug of firefox? I should also mention that I'm using the developer edition of firefox.

Alle Antworten (4)

more options

It works for me in Nightly.

more options

You're right, it seems like it works on both, regular firefox and nightly, just not on the developer version. I guess I've to wait for an update of the developer version then and use any of the other ones in the meantime?

Geändert am von Einhornyordle

more options

This is strange. May be a bug in dev-ed (so it will be solved n 4 weeks). I would also compare about:config entries beginning with dom.keyboardevent.*.

more options

dom.keyboardevent.* config entries are equal on all 3 editions, so that doesn't seem to be the problem. I guess I'll try again in a month or so.