keyboards | Open Source Keyman keyboards | Keyboard library

As mentioned in the above edit, I'd been poking at this issue here and there for the better part of a month before I finally figured it out. Most of what I read implied that the keyboardShouldPersistTaps prop should go on the component that's the next level up from the TextInput - in my case, the ScrollView component. In my case, this was not true.

In my case, the keyboardShouldPersistTaps prop had to go not on the next higher level component, but rather the highest level component that the user interacts with. For me, this was a SectionList, within each TextInput was rendered.

Maybe you could simply use this regexp value.replace(/[^0-9]/, '')

If you want to manage the copy and past as well, use the global flag:
value.replace(/[^0-9]/g, '')

You are using more than one Router. The nested router around the links is handling the links being clicked and updates the URL in the address bar, but this doesn't allow the outer router handling the routes to be made aware of the address change (until you reload the page).

Remove the nested Router, you need only one routing context for the entire app.

This is because in your index.js you are including and then . For not showing Home you should include it into App as another route. Eg.:

index.js

Try below code instead - I am not too happy with the this here

The simplest way is to set the action's short cut at design time using the Object Inspector:

But if you need to set this property programmatically, you can do

The issue you are running into here is related to how HTML and Javascript allows and handles input from the user. This is because a button input is not always in a 'focused' state read more here, and hence, Javascript is not receiving input events from the element as the button is not strictly receiving any.

The way to resolve this issue is realistically through CSS. The method most commonly used is using a standard text input field as shown below which is autofocused and maybe as a listener to always re-focus the element incase the user clicks outside of it.

I think the issue is with your AnimationMixer.update() call. If you look at the docs, update is expecting a time-delta in seconds, but it looks like you're passing the total running time. This means it should receive the time passed since the last frame. You can fix this by using clock.getDelta(); as the argument:

Yes, it's possible, for example, switch onscreen keyboard layout to Slovakia at runtime, in kotlin: