[TIMOB-16695] Android: HTML element inside webview is not working on Android version 4.4.2
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Not Our Bug |
Resolution Date | 2014-05-09T23:38:01.000+0000 |
Affected Version/s | Release 3.2.3 |
Fix Version/s | n/a |
Components | Android |
Labels | qe-3.2.3, triage |
Reporter | Priya Agarwal |
Assignee | Eric Wieber |
Created | 2014-03-25T11:03:59.000+0000 |
Updated | 2014-10-15T22:57:31.000+0000 |
Description
This is not a regression.
Since issue reproduces on 3.2.2.GA,3.2.1.GA
Steps to Reproduce:
1. Copy Paste the code given Below and run the app
Expected Result:
Window opens with webview rendering textField from html page.
Actual Result:
Window getting displayed as"file:///concerto/ClientScripts/TouchTestWeb"
Studio Logs Attached.
app.js
var win = Ti.UI.createWindow();
var web = Ti.UI.createWebView({
height: Ti.UI.FILL,
width: Ti.UI.FILL,
url: 'textfield.html'
});
win.add(web);
win.open();
textfield.html
<html>
<head>
<title>Test for textfields</title>
</head>
<body>
<form>
First name: <input type="text" name="firstname"><br>
Last name: <input type="text" name="lastname">
</form>
</body>
</html>
Attachments
File | Date | Size |
---|---|---|
studioConsoleLog.txt | 2014-03-25T11:03:59.000+0000 | 18993 |
This started happening to me all of a sudden. All of my webviews are broken. Is there any partial solution/workaround?
So this happens on Android 4.4.2 because of the breaking changes of the Webkit-based Webview. Migration guide [here](http://developer.android.com/guide/webapps/migrating.html) . My apps are broken because of this and I can't see the bright light at the end of the tunnel (the ticket has been reported 3 weeks ago)
We are seeing this issue occur when services are enabled for a project that is trying to run on Android 4.4. More specifically, the SOASTA touchtest module is the culprit. Removing the module from your project should allow the webviews to render properly. If you experience different, please let us know. We have informed SOASTA of this and they are working on the fix. They currently have this scheduled for June, but we have asked them to make this more of a priority.
According to the logs, this is a known Soasta bug and we are waiting for a Fix, solving as not our bug
A fix for this went out with the last SOASTA update. I no longer encounter this issue with my apps. Closing.