Congratulations and thank you for breaking the ice @rafiq!
The background to this behaviour is that there is a bug with Crosswalk WebView versions 16 and higher that causes the app display to flicker when opening the on-screen keyboard.
One workaround for this issue is to force the Crosswalk rendering engine to use SurfaceView instead of TextureView.
We’ve made this the default setting in the platform but it does, unfortunately, come at the cost of breaking modules that need to launch additional Crosswalk windows. For example,
Therefore, if you are using the
forge.tabs module with a
crosswalk build you will need to set the value of the “Enable Animatable Xwalk View” property to
true in your
If you are now experiencing flickering when opening the on-screen keyboard you can use the second workaround for this issue which is to set the “Window Soft Input Mode” property to
"adjustPan" in your
This workaround will resolve the flickering, albeit at the cost of the WebView no longer scrolling up when the on-screen keyboard is opened.
The workaround for this depends on your web framework of choice, but a good place to start would be StackOverflow.
tl;dr If you want to use
forge.tabs with the
crosswalk target you need to:
- Manually handle keyboard show/hide events to ensure your form inputs aren’t obscured.
It’s not ideal and it looks like it may be a while still before the Crosswalk team can resolve the underlying problems.
For more background information see: XWALK-3547 -
XWalkView window stretches momentarily when hiding native ui elements.