Revert "Allow MessageFilters to restrict listening to specific message classes"

content/browser/renderer_host/clipboard_message_filter.cc

 // 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.
 
 #include "content/browser/renderer_host/clipboard_message_filter.h"
 
 #include "base/bind.h"
 #include "base/bind_helpers.h"
 #include "base/location.h"
 #include "base/memory/scoped_ptr.h"
@@ skipping 16 matching lines @@
 // the "owner" of the clipboard's contents. See http://crbug.com/5823.
 void WriteObjectsOnUIThread(ui::Clipboard::ObjectMap* objects) {
   DCHECK(BrowserThread::CurrentlyOn(BrowserThread::UI));
   static ui::Clipboard* clipboard = ui::Clipboard::GetForCurrentThread();
   clipboard->WriteObjects(ui::CLIPBOARD_TYPE_COPY_PASTE, *objects);
 }
 
 }  // namespace
 
 
-ClipboardMessageFilter::ClipboardMessageFilter()
-    : BrowserMessageFilter(ClipboardMsgStart) {}
+ClipboardMessageFilter::ClipboardMessageFilter() {}
 
 void ClipboardMessageFilter::OverrideThreadForMessage(
     const IPC::Message& message, BrowserThread::ID* thread) {
   // Clipboard writes should always occur on the UI thread due the restrictions
   // of various platform APIs. In general, the clipboard is not thread-safe, so
   // all clipboard calls should be serviced from the UI thread.
   //
   // Windows needs clipboard reads to be serviced from the IO thread because
   // these are sync IPCs which can result in deadlocks with NPAPI plugins if
   // serviced from the UI thread. Note that Windows clipboard calls ARE
@@ skipping 189 matching lines @@
 
 // static
 ui::Clipboard* ClipboardMessageFilter::GetClipboard() {
   // We have a static instance of the clipboard service for use by all message
   // filters.  This instance lives for the life of the browser processes.
   static ui::Clipboard* clipboard = ui::Clipboard::GetForCurrentThread();
   return clipboard;
 }
 
 }  // namespace content