Chromium Code Reviews| Index: remoting/client/plugin/pepper_view.cc |
| diff --git a/remoting/client/plugin/pepper_view.cc b/remoting/client/plugin/pepper_view.cc |
| index c893d0bd6d95289e92a5ce3f35ba3527438fdb82..8d0a3b908d2d0349e5f81226edb16e9fa2eedab9 100644 |
| --- a/remoting/client/plugin/pepper_view.cc |
| +++ b/remoting/client/plugin/pepper_view.cc |
| @@ -237,7 +237,6 @@ void PepperView::SetConnectionState(protocol::ConnectionToHost::State state, |
| break; |
| case protocol::ConnectionToHost::CONNECTED: |
|
Wez
2011/11/03 00:25:02
Is there any point in keeping this case?
Sergey Ulanov
2011/11/03 01:21:12
Yes, to avoid compiler warnings, otherwise I would
|
| - scriptable_obj->SignalLoginChallenge(); |
| break; |
| case protocol::ConnectionToHost::AUTHENTICATED: |
| @@ -260,20 +259,6 @@ void PepperView::SetConnectionState(protocol::ConnectionToHost::State state, |
| } |
| } |
| -void PepperView::UpdateLoginStatus(bool success, const std::string& info) { |
| - DCHECK(context_->main_message_loop()->BelongsToCurrentThread()); |
| - |
| - // TODO(hclam): Re-consider the way we communicate with Javascript. |
| - ChromotingScriptableObject* scriptable_obj = instance_->GetScriptableObject(); |
| - if (success) { |
| - scriptable_obj->SetConnectionStatus( |
| - ChromotingScriptableObject::STATUS_CONNECTED, |
| - ChromotingScriptableObject::ERROR_NONE); |
| - } else { |
| - scriptable_obj->SignalLoginChallenge(); |
| - } |
| -} |
| - |
| bool PepperView::SetPluginSize(const SkISize& plugin_size) { |
| if (plugin_size_ == plugin_size) |
| return false; |