Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-24110] iOS: Expose keyboardDisplayRequiresUserAction property in Ti.UI.WebView

GitHub Issuen/a
TypeNew Feature
PriorityMedium
StatusClosed
ResolutionFixed
Resolution Date2016-11-14T10:43:12.000+0000
Affected Version/sn/a
Fix Version/sRelease 6.1.0
ComponentsiOS
Labelscommunity, ios, notable, webview
ReporterFlavio De Stefano
AssigneeHans Knöchel
Created2016-11-07T10:36:00.000+0000
Updated2016-11-18T21:35:16.000+0000

Description

When this property is set to true, the user must explicitly tap the elements in the web view to display the keyboard (or other relevant input view) for that element. When set to false, a focus event on an element causes the input view to be displayed and associated with that element automatically. The default value for this property is true.

Comments

  1. Flavio De Stefano 2016-11-07

    Test case:
       var win = Ti.UI.createWindow();
       var web = Ti.UI.createWebView({
       	keyboardDisplayRequiresUserAction: false,
       	top: 50,
       	html: '<input type="text" id="casa" /><script>setTimeout(function(){ document.getElementById(\'casa\').focus(); }, 1000);</script>'
       });
       
       win.add(web);
       win.open();
       
  2. Hans Knöchel 2016-11-12

    PR: https://github.com/appcelerator/titanium_mobile/pull/8588 Unit-Test: https://github.com/appcelerator/titanium-mobile-mocha-suite/pull/12
  3. Abir Mukherjee 2016-11-18

    Using this environment: Node Version: 4.5.0 Mac OS: 10.12.1 Appc CLI: 6.0.0 Appc CLI NPM: 4.2.8 Titanium SDK version: 6.1.0.v20161116071014 Appcelerator Studio, build: 4.8.0.201611121409 Xcode 8.1 GM Device: iOS 10.1.1 Installed the app on device (also with Simulator), and found that with keyboardDisplayRequiresUserAction set to true, the user had to click on the element to use the keyboard, or enter information on the field. With the property set to false, I found that when I opened the app, element was already enabled, and a cursor was blinking in the field. Lastly, with the property commented out, the behavior was same as set to true, i.e. default value verified to be set to true. The feature is working as expected.

JSON Source