Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Keydown event for Escape key not being registered

  • 2 답장
  • 0 이 문제를 만남
  • 1 보기
  • 최종 답변자: fkkd33

more options

At some point, I've noticed that certain behaviours expected to occur when pressing the Escape key no longer did. Those behaviours mainly involved triggering some Javascript, including functionality in keyboard-related extensions, such as Tridactyl. Browser-level functionality on the other hand, such as pressing Shift-Escape to open `about:processes`, or pressing Escape to close Search Suggestions when the URL input bar, continue to work as before.

Upon investigation, I found it is specifically the javascript Keydown event that isn't being registered, while the subsequent Keyup event still is. I used https://w3c.github.io/uievents/tools/key-event-viewer.html to test this.

I also found that starting Firefox in Troubleshoot Mode (Safe mode) doesn't resolve the issue. On the other hand, creating a new profile does.

I've looked at the modified settings in `about:config`; there's a lot, but nothing stands out as being related to keyboard input or javascript.

Can someone please help me find what is causing this?

At some point, I've noticed that certain behaviours expected to occur when pressing the Escape key no longer did. Those behaviours mainly involved triggering some Javascript, including functionality in keyboard-related extensions, such as Tridactyl. Browser-level functionality on the other hand, such as pressing Shift-Escape to open `about:processes`, or pressing Escape to close Search Suggestions when the URL input bar, continue to work as before. Upon investigation, I found it is specifically the javascript Keydown event that isn't being registered, while the subsequent Keyup event still is. I used https://w3c.github.io/uievents/tools/key-event-viewer.html to test this. I also found that starting Firefox in Troubleshoot Mode (Safe mode) doesn't resolve the issue. On the other hand, creating a new profile does. I've looked at the modified settings in `about:config`; there's a lot, but nothing stands out as being related to keyboard input or javascript. Can someone please help me find what is causing this?

모든 댓글 (2)

more options

You can look at dom.keyboardevent prefs.

more options

cor-el said

You can look at dom.keyboardevent prefs.

Unfortunately, they are all default and identical to the new test profile I created.