We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Этот сайт имеет ограниченную функциональность, пока мы проводим техническое обслуживание для улучшения его работы. Если какая-либо статья не решила вашу проблему и вы хотите задать вопрос, наше сообщество поддержки ждёт вас: @FirefoxSupport в Твиттере и /r/firefox на Reddit.

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

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

  • 4 ответа
  • 1 имеет эту проблему
  • 7 просмотров
  • Последний ответ от 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.

Все ответы (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?

Изменено 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.