Change the lifetime of the WebKit thread to be a subset of the IO thread's li...

chrome/browser/chrome_thread.cc

Index: chrome/browser/chrome_thread.cc
===================================================================
--- chrome/browser/chrome_thread.cc	(revision 20100)
+++ chrome/browser/chrome_thread.cc	(working copy)
@@ -9,6 +9,7 @@
   "Chrome_IOThread",  // IO
   "Chrome_FileThread",  // FILE
   "Chrome_DBThread",  // DB
+  "Chrome_WebKitThread",  // WEBKIT
   "Chrome_HistoryThread",  // HISTORY
 #if defined(OS_LINUX)
   "Chrome_Background_X11Thread",  // BACKGROUND_X11
@@ -21,6 +22,7 @@
   NULL,  // IO
   NULL,  // FILE
   NULL,  // DB
+  NULL,  // WEBKIT
   NULL,  // HISTORY
 #if defined(OS_LINUX)
   NULL,  // BACKGROUND_X11
@@ -51,3 +53,13 @@
 
   return NULL;
 }
+
+// static
+bool ChromeThread::CurrentlyOn(ID identifier) {
+  // MessageLoop::current() will return NULL if none is running.  This is often
+  // true when running under unit tests.  This behavior actually works out
+  // pretty convienently (as is mentioned in the header file comment), but it's
+  // worth noting here.
+  MessageLoop* message_loop = GetMessageLoop(identifier);
+  return MessageLoop::current() == message_loop;
+}