Updates touch calibration API and plumbs through the native touch calibration method

chrome/browser/resources/settings/device_page/display.js

Index: chrome/browser/resources/settings/device_page/display.js
diff --git a/chrome/browser/resources/settings/device_page/display.js b/chrome/browser/resources/settings/device_page/display.js
index 3cb387976e86c7ebc47ba328281b9231e53303a5..7a48f33b900f79511ffc37a238ca48135fe6552d 100644
--- a/chrome/browser/resources/settings/device_page/display.js
+++ b/chrome/browser/resources/settings/device_page/display.js
@@ -315,8 +315,8 @@ Polymer({
    * @private
    */
   onTouchCalibrationTap_: function(e) {
-    settings.display.systemDisplayApi.touchCalibrationStart(
-        this.selectedDisplay.id);
+    settings.display.systemDisplayApi.showNativeTouchCalibration(
+        this.selectedDisplay.id, function(success) {});

[stevenjb, 2017/01/19 17:19:01]

Ideally we should disable the button while touch calibration is in progress and
enable it when it completes. In order to do that robustly however we would also
need to be able to query whether calibration is in progress when we load the UI,
so maybe add a TODO here instead and file a bug for that.

In the meanwhile, if we make the callback optional, no need to pass an empty
function.

[malaykeshav, 2017/01/19 23:49:07]

This would be a safety measure since the calibration UX overlays the entire
screen. And the user cannot interact with anything other than the touch
calibration UX while it is in progress.

   },
 
   /**