Move HiDPI-related Pepper interfaces to stable

ppapi/api/ppb_view.idl

Index: ppapi/api/ppb_view.idl
diff --git a/ppapi/api/ppb_view.idl b/ppapi/api/ppb_view.idl
index cc61ed20f16f1302e8feaf1871d983af5b956ce7..a01c5e828d3ba1cbc0cce2f52c60a54f6034fbc0 100644
--- a/ppapi/api/ppb_view.idl
+++ b/ppapi/api/ppb_view.idl
@@ -11,7 +11,8 @@
 [generate_thunk]
 
 label Chrome {
-  M18 = 1.0
+  M18 = 1.0,
+  M28 = 1.1
 };
 
 /**
@@ -159,5 +160,38 @@ interface PPB_View {
    */
   PP_Bool GetClipRect([in] PP_Resource resource,
                       [out] PP_Rect clip);
+
+  /**
+   * GetDeviceScale returns the scale factor between device pixels and Density
+   * Independent Pixels (DIPs, also known as logical pixels or UI pixels on
+   * some platforms). This allows the developer to render their contents at
+   * device resolution, even as coordinates / sizes are given in DIPs through
+   * the API.
+   *
+   * Note that the coordinate system for Pepper APIs is DIPs. Also note that
+   * one DIP might not equal one CSS pixel - when page scale/zoom is in effect.
+   *
+   * @param[in] resource A <code>PP_Resource</code> corresponding to a
+   * <code>PPB_View</code> resource.
+   *
+   * @return A <code>float</code> value representing the number of device pixels
+   * per DIP. If the resource is invalid, the value will be 0.0.
+   */
+  [version=1.1]
+  float_t GetDeviceScale([in] PP_Resource resource);
+
+  /**
+   * GetCSSScale returns the scale factor between DIPs and CSS pixels. This
+   * allows proper scaling between DIPs - as sent via the Pepper API - and CSS
+   * pixel coordinates used for Web content.
+   *
+   * @param[in] resource A <code>PP_Resource</code> corresponding to a
+   * <code>PPB_View</code> resource.
+   *
+   * @return css_scale A <code>float</code> value representing the number of
+   * DIPs per CSS pixel. If the resource is invalid, the value will be 0.0.
+   */
+  [version=1.1]
+  float_t GetCSSScale([in] PP_Resource resource);
 };