some additional information: the bouncing keyboard was in FileMaker Go 11 and seems to be fixed in 12. However in 12, the delay caused by the script with the find routine does not really allow for fast typing and when you do, it skipts characters ...
When I implement this find-as-you-type behavior, I always use a two-trigger approach. An OnObjectModify trigger attached to the field installs an OnTimer trigger to run shortly after the OnObjectModify script ends — typically in the neighborhood of .3 seconds. Only the OnTimer script actuall performs any find. (The OnTimer script should also uninstall itself when it's finished.) This way, if the user is typing at even a modest pace, each keystroke resets the OnTimer trigger. The find only happens when there's a pause in the user's typing. The end result is that the interface is much more responsive, actual finds are performed less frequently, and finds usually have a smaller found set, which pushes less data over the network.
thanks again for your tip! This really does the tric :-)
best regards - Dick