Add PPB_Fullscreen;0.5.

ppapi/api/dev/ppb_fullscreen_dev.idl

 /* Copyright (c) 2011 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.
  */
 
 
 /**
  * This file defines the <code>PPB_Fullscreen</code> interface.
  */
 
 label Chrome {
   M14 = 0.4
 };
 
 interface PPB_Fullscreen_Dev {
   /**
    * Checks whether the plugin instance is currently in fullscreen mode.
    */
   PP_Bool IsFullscreen(
       [in] PP_Instance instance);
 
   /**
    * Switches the plugin instance to/from fullscreen mode. Returns PP_TRUE on
    * success, PP_FALSE on failure.
    *
    * This unbinds the current Graphics2D or Surface3D. Pending flushes and
-   * swapbuffers will execute as if the resource was off-screen.  The transition
-   * is asynchronous. During the transition, IsFullscreen will return PP_False,
+   * swapbuffers will execute as if the resource was off-screen. The transition
+   * is asynchronous. During the transition, IsFullscreen will return PP_FALSE,
    * and no Graphics2D or Surface3D can be bound. The transition ends at the
-   * next DidChangeView.
+   * next DidChangeView. The transition from fullscreen is synchronous.
    *
    * Note: when switching to and from fullscreen, Context3D and Surface3D
    * resources need to be re-created. This is a current limitation that will be
    * lifted in a later revision.
    */
   PP_Bool SetFullscreen(
       [in] PP_Instance instance,
       [in] PP_Bool fullscreen);
 
   /**
-   * Gets the size of the screen. When going fullscreen, the instance will be
-   * resized to that size.
+   * Gets the logical size (aka resolution) of the screen in pixels.
+   * When going fullscreen, the instance will be resized to that size.
    */
   PP_Bool GetScreenSize(

[piman, 2011/09/09 01:33:44]

Maybe we can remove this function from the Dev interface because it has the
exact same implementation (and purpose) as the stable one.

[polina, 2011/09/26 21:57:00]

I don't think we should since the double-interface situation is temporary. This
will require combined usage of the two interfaces, which can complicate things.

       [in] PP_Instance instance,
       [out] PP_Size size);
 };