Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Learn More

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Keydown event for Escape key not being registered

  • 2 antwurd
  • 0 hawwe dit probleem
  • 29 werjeftes
  • Lêste antwurd fan 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?

Alle antwurden (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.