Formatting changes

ppapi/api/pp_input_event.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 API used to handle mouse and keyboard input events.
  */
 
 /**
@@ skipping 110 matching lines @@
  * events.
  */
 [assert_size(24)] struct PP_InputEvent_Wheel {
   /**
    * This value represents a combination of the <code>EVENT_MODIFIER</code>
    * flags.
    */
   uint32_t modifier;
 
   /**
-   * Indicates the amount vertically and horizontally the user has requested
-   * to scroll by with their mouse wheel. A scroll down or to the right (where
-   * the content moves up or left) is represented as positive values, and
-   * a scroll up or to the left (where the content moves down or right) is
+   * The mouse wheel's horizontal scroll amount. A scroll to the right
+   * (where the content moves left) is represented as positive values,
+   * and a scroll to the left (where the content moves right) is
    * represented as negative values.
    *
    * The units are either in pixels (when scroll_by_page is false) or pages
    * (when scroll_by_page is true). For example, delta_y = -3 means scroll up 3
    * pixels when scroll_by_page is false, and scroll up 3 pages when
    * scroll_by_page is true.
    *
    * This amount is system dependent and will take into account the user's
    * preferred scroll sensitivity and potentially also nonlinear acceleration
    * based on the speed of the scrolling.
    *
    * Devices will be of varying resolution. Some mice with large detents will
    * only generate integer scroll amounts. But fractional values are also
    * possible, for example, on some trackpads and newer mice that don't have
    * "clicks".
    */
   float_t delta_x;
 
-  /** This value represents */
+  /**
+   * The mouse wheel's vertical scroll amount. A scroll down (where the
+   * content moves up) is represented as positive values, and a scroll up
+   * (where the content moves down) is represented as negative values.
+   *
+   * The units are either in pixels (when scroll_by_page is false) or pages
+   * (when scroll_by_page is true). For example, delta_y = -3 means scroll up 3
+   * pixels when scroll_by_page is false, and scroll up 3 pages when
+   * scroll_by_page is true.
+   *
+   * This amount is system dependent and will take into account the user's
+   * preferred scroll sensitivity and potentially also nonlinear acceleration
+   * based on the speed of the scrolling.
+   *
+   * Devices will be of varying resolution. Some mice with large detents will
+   * only generate integer scroll amounts. But fractional values are also
+   * possible, for example, on some trackpads and newer mice that don't have
+   * "clicks".
+   */
   float_t delta_y;
 
   /**
    * The number of "clicks" of the scroll wheel that have produced the
    * event. The value may have system-specific acceleration applied to it,
    * depending on the device. The positive and negative meanings are the same
    * as for <code>delta_x</code> and <code>delta_y</code>.
    *
    * If you are scrolling, you probably want to use the delta values above.
    * These tick events can be useful if you aren't doing actual scrolling and
@@ skipping 13 matching lines @@
   float_t wheel_ticks_y;
 
   /**
    * Indicates if the scroll <code>delta_x</code>/<code>delta_y</code>
    * indicates pages or lines to scroll by. When true, the user is requesting
    * to scroll by pages.
    */
   PP_Bool scroll_by_page;
 };