topic Thr image is about Android, in Software Archive

Serious graphical issues in Android

Alessandro_S_ — Fri, 25 Sep 2015 07:55:31 GMT

I have this kind of problem (Android Devices)

Build Android CLI 5.1.1

When I move on text fields, the keyboards pulls everything up but many times graphical leaks occur. The app remains lower or upper than original position. Of course this is unaccettable. I've attached a screenshot

Build Android Crosswalk 15 (I need CLI 5.1.1)

(With the previous version of XDK I could choose Crosswalk 10 that fixed the bug I'm going to mention)

The keyboard overlaps the textfield and I cannot see what I'm writing. Of course this is unaccettable.

Is there any trick to use in css or something like that? please help me, I cannot release because everytime there's an issue not completely depending on me.

We'll report this issue to

PaulF_IntelCorp — Fri, 25 Sep 2015 16:46:47 GMT

We'll report this issue to the Crosswalk project team, it appears to be an issue there. In the meantime, you might also checkout using the Ionics keyboard plugin to manage the keyboard. To add it to your project, goto the third-party plugin section of the plugin manager, make sure "cordova plugin registry" is selected and type ionic-plugin-keyboard into the plugin ID field. See https://github.com/driftyco/ionic-plugin-keyboard for documentation for this third-party plugin.

I already used ionic but I

Alessandro_S_ — Fri, 25 Sep 2015 17:03:54 GMT

I already used ionic but I cannot fix the problem of android build. See attachment. In this moment I dont want to use crosswalk because the size of the apk so I must solve the graphical issue in abdroid. Can anyone help me?

So are you saying the image

PaulF_IntelCorp — Fri, 25 Sep 2015 17:21:05 GMT

So are you saying the image you provided is something you are seeing with an Android build or with a Crosswalk build? If you are seeing this with an Android build there's not much we (the XDK) can do about that. This is why we offer the Crosswalk build, it solves many of the problems associated with the inconsistent Android webviews.

Is your sample image from an Android or Crosswalk build?

Thr image is about Android,

Alessandro_S_ — Fri, 25 Sep 2015 17:29:57 GMT

Thr image is about Android, while crosswalk 15 has keyboard over input. I think that I could use ionic keyboardhide event to impose the view refresh so the window come back to correct position...I need something like window.moveto (0,0)...i tried with no success. Is there any jquery/html5/js command?

I switched my project to CLI

John_C_6 — Fri, 25 Sep 2015 18:26:00 GMT

I switched my project to CLI 5.1.1 and Crosswalk 15.
Attached you will find the problems with Xwalk 15:
- Bad font antialias
- Repaint regions not working properly (continuously). The same kind of glitches that Alessandro has.
- Some rounded DIVs (border-radius:50%) not working at all ...

(tested under Sony Xperia Z - 4.2.2)

We have alerted the Crosswalk

PaulF_IntelCorp — Fri, 25 Sep 2015 22:47:45 GMT

We have alerted the Crosswalk team regarding the issues you are reporting.

I'm trying to reproduce the

Francesco_B_Intel1 — Sat, 26 Sep 2015 07:57:16 GMT

I'm trying to reproduce the issues with Crosswalk 15. If anybody has sample code that demonstrates the problems that would be very helpful. Also, does Crosswalk 14 (the current stable release) behave any better?

Under Crosswalk 14, it works

John_C_6 — Sat, 26 Sep 2015 17:25:34 GMT

Under Crosswalk 14, it works perfectly (but it has a bug with soft keyboard which causes a small flickering when showing/hiding it).
In the Xwalk 15, I think the problems are related to the change in SurfaceView default switch (my app use a lot of transparents DIVs). IMHO, this change is not production ready.

The flickering when showing

Francesco_B_Intel1 — Mon, 28 Sep 2015 07:33:06 GMT

The flickering when showing/hiding the keyboard is exactly the reason we made surfaceView the default. We should probably expose the view type as a setting so that users can decide what is best for them (e.g. Ionic users have been using surfaceView for some time)