I've tested ctrl, shift, and blue arrow (also thought about it) - bug still exist.

Yet, thanks to Your suggestion with xev, I've noticed something, which makes this bug even more strange. Xev doesn't have anything to tell about it - just like it doesn't happen (register one click). Then, trying it again with xvkbd, it seems that I was wrong initially - it *isn't* long-press. Long press looks different - xvkbd key becomes "black" (virtually pushed down), and keys repeat quite fast.

In case of my bug, after initial press, xvkbd doesn't look pressed at all, and keys keep repeating at quite slow rate (I called it "moderate" in last post). It looks, like just having cursor over xvkbd key, makes it repeat.

On the other hand, if I *really* long-press some xvkbd key (making it repeat quickly), and then lift stylus (stop it, not touching screen anymore), keys are *not* repeating - of course, until I tap on other key. So, long press before, negates strange "repeating" presses.

I have no fckn clue about what is happening here...

BTW - on other parts that xvkbd, it isn't 100% reproducible - most times, tapping is recognized properly (as one click) - yet, when I try some clicks repeatedly (for example, switching between 4 available LXDE desktops), it start to appear as long-press (submenu appear 0.5 second or so after tap).

Trying the same on xvkbd, I can *never* make it to register "real" long-press wrongly (i.e, key *never* look like pressed - black, pushed down, etc) - of course, unless i long-press it really.

Very strange, but, overall, for other scenarios that using xvkbd, it isn't entirely critical, so I'm going to publish my image - I wonder what other people reports will be. Still, any clues *highly* appreciated.

So, I'm using Scrollbars Anywhere (Chromium) from the very beginning, and it's working great. As for Iceweasel, I haven't tested it - I'm not using it any longer.