Additional strategies for ICEmobile-SX need to be investigated. For instance, Chrome is likely attempting to ensure that user submitted data isn't lost. To handle this, it may be possible for ICEmobile-SX components to trigger a form submit to the server, then cause the ICEmobile-SX action to occur from the returned page.

(The disadvantage of this is that it will not work offline.)

Placing the input text outside the form also results in the creation of a new tab.

Setting image dimensions in mobileshowcase also results in a new tab being created. This means that an ajax update to the form does not convince Chrome that the user data on the page has been submitted.

As advised by stack overflow for ICS versions of Android, the following was tried, but did not help:

browserIntent.setFlags(Intent.FLAG_FROM_BACKGROUND | Intent.FLAG_ACTIVITY_REORDER_TO_FRONT | Intent.FLAG_ACTIVITY_NEW_TASK);

The solution attempted above was actually for the stock android browser, not Chrome. I have done some additional googling, but have not unearthed any new findings. I searched the chromium project source code as well, but could not find any intent processing logic related to creation of new tabs. I don't thing the production activity lives in the open source, as I could only find test shell activities.

We should enter an issue with the chromium project.

https://code.google.com/p/chromium/issues

Issue reported:

https://code.google.com/p/chromium/issues/detail?id=262242

svn 38248: The following code works on Chrome and Android stock browser to eliminate extra tabs and page reloads. It does not work for Firefox (known issue).

final ResolveInfo res = getPackageManager().resolveActivity(browserIntent,PackageManager.MATCH_DEFAULT_ONLY);
if (res.activityInfo != null)

Verified fixed.