Ghjuvan Lacambre

Right, I just noticed this while answering another issue. I've reverted c8cd51c3e04a1b1a12cfa21b6b9aaf62c16b983f in 804d6c4bbbdc7f4b679617f88f8136e3b38bee37 until I figure out what's wrong. Thanks for the report!

Hi, thanks you for trying Firenvim. Could you try to go through the steps of the troubleshooting guide ( https://github.com/glacambre/firenvim/blob/master/TROUBLESHOOTING.md ) and let me know what the result is?

Oh, I see, I thought you meant that Firenvim didn't work at all. I can't try it at the moment but I suspect I will be able to reproduce this...

Huh, actually it looks like there aren't any CSP/security issues here, the editor seems to swallow the focus event that Firenvim relies on. Using ```vim let g:firenvim_config = { \...

This is surprising to hear, I'm getting 60 fps scrolling in fullscreen and that's with integrated graphics. What is the size of the neovim frame in pixels? What CPU and...

>Please let me know if you need any further information. I'd like to know what CPU & GPU you are using and the dimensions of the Firenvim frame in pixels...

Thank you for trying another machine - can you confirm that the dimensions of the Firenvim frame were the same?

Does changing your [alt](https://github.com/glacambre/firenvim#special-characters-on-osx) setting to `all` fix this issue?

The browser sees the event, translates it into a representation Neovim understands and then sends it to neovim with `nvim_input`. This is done in two places: - In a [keydown...

https://bugzilla.mozilla.org/show_bug.cgi?id=1731521