Making sure that UAC promts fired by the Chromoting plugin get focus (instead of being shown in the…

remoting/host/plugin/host_script_object.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef REMOTING_HOST_PLUGIN_HOST_SCRIPT_OBJECT_H_
 #define REMOTING_HOST_PLUGIN_HOST_SCRIPT_OBJECT_H_
 
 #include <string>
 #include <vector>
 
@@ skipping 63 matching lines @@
   virtual void OnAccessDenied(const std::string& jid) OVERRIDE;
   virtual void OnClientAuthenticated(const std::string& jid) OVERRIDE;
   virtual void OnClientDisconnected(const std::string& jid) OVERRIDE;
   virtual void OnShutdown() OVERRIDE;
 
   // Post LogDebugInfo to the correct proxy (and thus, on the correct thread).
   // This should only be called by HostLogHandler. To log to the UI, use the
   // standard LOG(INFO) and it will be sent to this method.
   void PostLogDebugInfo(const std::string& message);
 
+  void SetWindow(NPWindow* np_window);
+
  private:
   // These state values are duplicated in the JS code. Remember to update both
   // copies when making changes.
   enum State {
     kDisconnected,
     kStarting,
     kRequestedAccessCode,
     kReceivedAccessCode,
     kConnected,
     kDisconnecting,
@@ skipping 214 matching lines @@
   // SequencedWorkerPool. Problem is that SequencedWorkerPool relies
   // on MessageLoopProxy::current().
   base::Thread worker_thread_;
 
   DISALLOW_COPY_AND_ASSIGN(HostNPScriptObject);
 };
 
 }  // namespace remoting
 
 #endif  // REMOTING_HOST_PLUGIN_HOST_SCRIPT_OBJECT_H_