Webbrowser issues on Android

[nickk...@gmail.com]

I'm having multiple issues with the web browser component on Android, it these issues don't appear on iOS and in the simulator it is generally OK as well.

The set up is a form with a border layout and the only component is a webbrowser in the center and a number of other forms that don't have the web browser component - these are laid out in the original UI Builder. onPostShow for the form with the web browser in it the content is set to a stored string of HTML content (its not making a network request or anything for this content).

The app has a side menu, and a back command added to the title.

1. When the form is loaded an android loading indicator is shown over the page for around 30 seconds longer than it takes to actually load the content. I like the loading indicator, but it should disappear as soon as the content in the page is available.

2. The UI freezes just before the side menu closes, leaving it partially open while the loading indicator is shown, it looks very messy.

3. If you use the side menu to change to the page that holds the web browser then all subsequent forms have the web browser over the top.

4. If you use the back button (on screen or the device back button) then it reloads the webbrowser component and does actually navigate back to the previous form (or does navigate back to the previous form but continues to show the web browser component over the top?).

I fixed 3 to some extent by removing the webbrowser component from the form on exitForm however this causes multiple repainting and flickering while the side menu closes and the form changes. It didn't also fix issue 4.

I tried newPeer=true and it immediately crashes (Application has stopped) as soon as a form with a webbrowser is shown.

Any ideas what's going on here? It a fairly simple set up, using the side menu to switch between UIBuilder forms, one of which show s a webbrowser.

Cheers,

Nick

[Shai Almog]

If you get  a crash with the new peer mode please connect a cable and run DDMS. We need stack traces for potential issues here.

You can disable the browser component using:
Display.getInstance().setProperty("WebLoadingHidden", "true");

Unfortunately it's an "all or nothing" situation with the progress.

Except for the navigation issue which might be a regression most of these issues should be improved by the new peer API.