On WebBrower input text, keyboard doesn't appear. I can't make any edition

[hru...@gmail.com]

If you are experiencing an issue please mention the full platform your issue applies to:
IDE: NetBeans
Desktop OS
Simulator : on simulator all is OK.
Device: Moto G, and Galaxy Note 8

For the first time, I did tests using real devices with my App.

(Using: Smartphone Moto G da Motorola and Tablet Samsung Galaxy Note 8)

My App does intensive use of WebBrowser component and bi-directional

communication Java/Javascript.

The Application works correctly on simulator.

But,  the WebBrowser (in the devices tested)  presents the following  weird behaviors :

1) the font is extremely big and zoom-in and zoom-out  gestures don't work.

it makes impossible to fit the content into its space available and reading the content   confortably. 

2) When a field(<input type=text>)  gains the focus, the keyboard isn't shown and I can't editing anything inside it. 

I attached my html example.

[Steve Hannah]

1) the font is extremely big and zoom-in and zoom-out  gestures don't work.

it makes impossible to fit the content into its space available and reading the content   confortably. 

Use the BrowserComponent.setPinchZoomEnabled() method to enable pinch zoom.

https://codenameone.googlecode.com/svn/trunk/CodenameOne/javadoc/com/codename1/ui/BrowserComponent.html#setPinchToZoomEnabled(boolean)

 

2) When a field(<input type=text>)  gains the focus, the keyboard isn't shown and I can't editing anything inside it. 

Strange.  Does this happen with all text fields?  What if you create a simple example with only a single text field.  Does it still have the problem?

 

I attached my html example.

This form doesn't look too friendly for mobile.  You might want to look into some responsive web design strategies to make it more usable on smaller devices.

Steve

 

--
You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codenameone-discu...@googlegroups.com.
Visit this group at http://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/a4bd6807-34c0-410b-a0db-006f2d8bb934%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Steve Hannah

Web Lite Solutions Corp.

[hru...@gmail.com]

1) Strange.  Does this happen with all text fields?  What if you create a simple example with only a single text field.  Does it still have the problem?

  Yes. it occurs with all input text fields. I will try to use a simple html as you suggested to make a test.

2) This form doesn't look too friendly for mobile.  You might want to look into some responsive web design strategies to make it more usable on smaller devices.

Yes. I agree. This HTML is not good for mobile devices. But the client that contracted the application wants to use them. They already began to redesign them. They have a large legacy of HTML forms with this problem and the app needs to handle  that.

[hru...@gmail.com]

Shannah, Thank you.

I made test using your suggestion : BrowserComponent.setPinchZoomEnabled()  - method to enable pinch zoom.

Doing that resolved both problems listed within this post.

The keyboard is shown now when a input text field gains focus, and  I can use zoom-in and zoom-out on WebBrowser component.

[hru...@gmail.com]

I still have facing a problem about keyboard behavior.

There is a instability detected when App runs on my devices (Motorola - moto G and Galaxy tab 8 - Android 4.4).

When the screen that contains the webBrowser component is shown, all HTML-INPUT-Type=text don't recognizes correctly the touch over that field. The WebBrowser component shows a selection mark pointer  allowing cut-copy-paste but the keyboard isn't launched.

Then,  after some navigation (Tab change, internal navigation on HTML document, ...) where  I can't determine exactly which,  the webBrowser component begins to work correctly and the keyBoard is shown each time I touch over respective field.

Do You know any approach to solve that?

Obs: On simulator,  no problem. All works fine.    

[Shai Almog]

This is a known recurring issue in Android, it seems to be inherent in the browser there and keeps resurfacing despite the fact we adopted the original workarounds to this.
AFAIK this is experienced by others (natively in Android) and there is no definitive solution.
Maybe Chen has some insight on this.