Moving DidFinishLoad from RenderView to RenderFrame.

content/common/view_messages.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.
 
 // IPC messages for page rendering.
 // Multiply-included message file, hence no include guard.
 
 #include "base/memory/shared_memory.h"
 #include "base/process/process.h"
 #include "base/strings/string16.h"
@@ skipping 1265 matching lines @@
                     bool /* has_audio */)
 IPC_MESSAGE_ROUTED1(ViewHostMsg_MediaPausedNotification,
                     int64 /* player_cookie, distinguishes instances */)
 
 // Notifies the browser that we have session history information.
 // page_id: unique ID that allows us to distinguish between history entries.
 IPC_MESSAGE_ROUTED2(ViewHostMsg_UpdateState,
                     int32 /* page_id */,
                     content::PageState /* state */)
 
-// Notifies the browser that a frame finished loading.
-IPC_MESSAGE_ROUTED3(ViewHostMsg_DidFinishLoad,
-                    int64 /* frame_id */,
-                    GURL /* validated_url */,
-                    bool /* is_main_frame */)
-
 // Changes the title for the page in the UI when the page is navigated or the
 // title changes.
 IPC_MESSAGE_ROUTED3(ViewHostMsg_UpdateTitle,
                     int32 /* page_id */,
                     base::string16 /* title */,
                     blink::WebTextDirection /* title direction */)
 
 // Change the encoding name of the page in UI when the page has detected
 // proper encoding name.
 IPC_MESSAGE_ROUTED1(ViewHostMsg_UpdateEncoding,
@@ skipping 712 matching lines @@
 // synchronously (see crbug.com/120597). This IPC message sends the character
 // bounds after every composition change to always have correct bound info.
 IPC_MESSAGE_ROUTED2(ViewHostMsg_ImeCompositionRangeChanged,
                     gfx::Range /* composition range */,
                     std::vector<gfx::Rect> /* character bounds */)
 #endif
 
 // Adding a new message? Stick to the sort order above: first platform
 // independent ViewMsg, then ifdefs for platform specific ViewMsg, then platform
 // independent ViewHostMsg, then ifdefs for platform specific ViewHostMsg.