Touch Events capability negotiation

remoting/webapp/crd/js/client_plugin_impl.js

Index: remoting/webapp/crd/js/client_plugin_impl.js
diff --git a/remoting/webapp/crd/js/client_plugin_impl.js b/remoting/webapp/crd/js/client_plugin_impl.js
index 3560e7b8df1070e6de590a79716a59e0322e7248..2a20eb18025d25cdef5df5aba2614b428c6283fd 100644
--- a/remoting/webapp/crd/js/client_plugin_impl.js
+++ b/remoting/webapp/crd/js/client_plugin_impl.js
@@ -635,6 +635,16 @@ remoting.ClientPluginImpl.prototype.sendClipboardItem =
 };
 
 /**
+ * Notifies the plugin that touch events should be handled by the plugin.
+ *
+ * @return {void} Nothing.
+ */
+remoting.ClientPluginImpl.prototype.enableTouchEvents = function() {
+  this.plugin_.postMessage(
+      JSON.stringify({method: 'enableTouchEvents', data: {}}));

[Wez, 2015/03/30 17:10:07]

This makes enabling touch events a one-way function - once disabled you can
never disable them.

If you allow a bool enable/disable flag then we'd have the option of switching
touch events on or off based on user preferences, UX state, etc mid-session.

[Rintaro Kuroiwa, 2015/04/08 03:27:43]

Done.

+};
+
+/**
  * Notifies the host that the client has the specified size and pixel density.
  *
  * @param {number} width The available client width in DIPs.