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!

Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Keydown event for Escape key not being registered

  • 2 wotmołwje
  • 0 ma tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot 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?

Wšě wotmołwy (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.