Tridactyl can't respond to a continouous sequence of key events in textbox

[xiangsheng]

• Brief description of the problem:

  For any textbox in a page, with the tridactyl addon, I can't delete letters continuously by pressing the BACKSPACE key. That is, even if I keep pressing the BACKSPACE, I can only delete ONE letter. In fact, this bug is not limited to the BACKSPACE key alone. For example, I can't move the caret continuously by pressing the arrow keys. This bug seems to be introduced in recent version of tridactyl since I never notice this bug before.

• Steps to reproduce:

  Open any webpage. Anywhere in a textbox, keep pressing a key like BACKSPACE, SPACE, UP ... and observe the behaviour of the caret.

• Tridactyl version (:version):

  1.24.1pre7005-bd23136c

• Firefox version (Top right menu > Help > About Firefox):

  124.0.1(64bit)

• URL of the website the bug happens on:

  Any webpage except the pages owned by Firefox.

• Config (in a new tab, run :viewconfig --user, copy the url and paste it somewhere like gist.github.com):

  https://pastebin.com/ZTPvmN0r

[bovine3dom]

I haven't tried to reproduce this yet and won't be able to for a few days, but if it's really Tridactyl's fault it is probably because we are interfering with the repeat key events

[nyawox]

I have a similar issue. Instead of not responding to a continuous sequence of keys, I think the culprit may be that it doesn't respond correctly to certain types of rapid key events. Probably the easiest way to reproduce this is by using something like kanata sequences or qmk. This is huge for me because I have keys that output like this:

m (dynamic key) -> mp
m (dynamic key) -> (backspace) a p (space) -> map (space)

test (becoming key sequence) (whatsoever key sequence) outputs like this for me: testbe comingwh atsoever sometimes it becomes tesbe comingwh atsoever It always fails to backspace correctly. I've tried a handful of programs on linux, and only tridactyl has this issue.

[bovine3dom]

@nyawox where are you experiencing this? it is "expected" behaviour (a known bug) in the command line, you can work around it with

unbind --mode=ex <Space>
bind --mode=ex <A-Space> ex.insert_space_or_completion

I can't reproduce it in a text box.

@xiangsheng could you re-post your config? your link has expired, sorry. I can't reproduce your issue on my machine so something in your config (maybe an insert mode bind) is probably necessary

edit:

note to self - sleep 1; xdotool type "t the spaces in this will be wrong " is a handy snippet for testing this

[nyawox]

My bad, I was too high and missed the text box part. I was experiencing this issue specifically in the search bar, but your config fixed it! Thanks. It feels like a breeze to finally go back to using my familiar Tridactyl config without having to manually type one letter at a time instead of using sequences for common words.