Sorry you are face this problem. Setting the timeout at 800ms was indeed idiotic on my part. But at this point, I am wary of both – removing the feature entirely, or messing with the defaults, for fear of breaking the add-on for others.

Meanwhile, can you see if increasing the timeout to an impossibly long value resolves your issue? That should effectively disable the feature. But if you encountered the problem that

> The problem? Before long, perhaps with any Firefox update, this behavior has been turned on again, no matter how many times I have turned it off before.

then I think the impossibly long timeout time will also get reset.

I will look into fixing this issue as soon as time permits me.

Meanwhile, I will try to push out an update with a longer default timeout.