PPAPI: Take PPB_MessageLoop out of Dev

ppapi/api/ppb_message_loop.idl

 /* 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.
  */
 
 /**
- * Defines the PPB_MessageLoop_Dev interface.
+ * Defines the PPB_MessageLoop interface.
  */
 label Chrome {
-  M18 = 0.1
+  M25 = 1.0
 };
 
 /**
  * A message loop allows PPAPI calls to be issued on a thread. You may not
  * issue any API calls on a thread without creating a message loop. It also
  * allows you to post work to the message loop for a thread.
  *
  * To process work posted to the message loop, as well as completion callbacks
  * for asynchronous operations, you must run the message loop via Run().
  *
@@ skipping 96 matching lines @@
  *
  *   pp::CompletionCallback callback = factory_.NewOptionalCallback(...);
  *   int32_t result = message_loop.PostWork(callback);
  *   if (result != PP_OK_COMPLETIONPENDING)
  *     callback.Run(result);
  *
  * This will run the callback with an error value, and assumes that the
  * implementation of your callback checks the "result" argument and returns
  * immediately on error.
  */
-interface PPB_MessageLoop_Dev {
+interface PPB_MessageLoop {
   /**
    * Creates a message loop resource.
    *
    * This may be called from any thread. After your thread starts but before
    * issuing any other PPAPI calls on it, you must associate it with a message
    * loop by calling AttachToCurrentThread.
    */
   PP_Resource Create(PP_Instance instance);
 
   /**
@@ skipping 103 matching lines @@
    */
   int32_t PostWork([in] PP_Resource message_loop,
                    [in] PP_CompletionCallback callback,
                    [in] int64_t delay_ms);
 
   /**
    * Posts a quit message to the given message loop's work queue. Work posted
    * before that point will be processed before quitting.
    *
    * This may be called on the message loop registered for the current thread,
-   * or it may be called on the message loop registered for another thread.
+   * or it may be called on the message loop registered for another thread. It
+   * is an error to attempt to PostQuit() the main thread loop.
    *
    * @param should_destroy Marks the message loop as being in a destroyed state
    * and prevents further posting of messages.
    *
    * If you quit a message loop without setting should_destroy, it will still
    * be attached to the thread and you can still run it again by calling Run()
    * again. If you destroy it, it will be detached from the current thread.
    *
    * @return
    *   - PP_OK: The request to quit was successfully posted.
    *   - PP_ERROR_BADRESOURCE: The message loop was invalid.
    *   - PP_ERROR_WRONG_THREAD: You are attempting to quit the main thread.
    *     The main thread's message loop is managed by the system and can't be
    *     quit.
    */
   int32_t PostQuit([in] PP_Resource message_loop, PP_Bool should_destroy);
 };