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.

Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Keydown event for Escape key not being registered

  • 2 wótegronje
  • 0 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót 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šykne wótegrona (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.