Touch Events capability negotiation

remoting/client/plugin/chromoting_instance.cc

Index: remoting/client/plugin/chromoting_instance.cc
diff --git a/remoting/client/plugin/chromoting_instance.cc b/remoting/client/plugin/chromoting_instance.cc
index d4ad35f51487e7cefaacb8b8e3f58485fda627b0..1a3f1ed6bfffba8154359d56a03ff1e67f5897ad 100644
--- a/remoting/client/plugin/chromoting_instance.cc
+++ b/remoting/client/plugin/chromoting_instance.cc
@@ -179,7 +179,8 @@ const char ChromotingInstance::kApiFeatures[] =
     "pinlessAuth extensionMessage allowMouseLock videoControl";
 
 const char ChromotingInstance::kRequestedCapabilities[] = "";
-const char ChromotingInstance::kSupportedCapabilities[] = "desktopShape";
+const char ChromotingInstance::kSupportedCapabilities[] =
+    "desktopShape multiTouch";

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

Do you mean to add multiTouch capability here? You've already got the web-app
handling the capability negotiation.

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

I'm not very good at javascript :(
I found out that I could put it in webapp/base/js/application.js or just put it
here. I'll put it in application.js, where all the other app capabilities are
set.

[Wez, 2015/04/09 22:58:59]

My point is more that there are two sets of capability negotiations:
1. client <-> host (i.e. protocol level)
2. web-app <-> plugin (we needed this because the plugin used to be in-built to
Chrome).

If you add a capability here then it's #2, whereas I think you want #1?

[Rintaro Kuroiwa, 2015/04/20 18:20:03]

Oh I see. Yes I meant to do #1.

 
 ChromotingInstance::ChromotingInstance(PP_Instance pp_instance)
     : pp::Instance(pp_instance),