Pepper: Fix comments for PPB and PPP InputEvent.

ppapi/c/ppb_input_event.h

 /* 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.
  */
 
-/* From ppb_input_event.idl modified Mon Dec 16 15:35:15 2013. */
+/* From ppb_input_event.idl modified Thu Apr  3 14:52:10 2014. */
 
 #ifndef PPAPI_C_PPB_INPUT_EVENT_H_
 #define PPAPI_C_PPB_INPUT_EVENT_H_
 
 #include "ppapi/c/pp_bool.h"
 #include "ppapi/c/pp_instance.h"
 #include "ppapi/c/pp_macros.h"
 #include "ppapi/c/pp_point.h"
 #include "ppapi/c/pp_resource.h"
 #include "ppapi/c/pp_stdint.h"
@@ skipping 310 matching lines @@
    * do optimizations for scroll or touch events that can be processed
    * substantially faster if it knows there are no non-default receivers for
    * that message. Requesting that such messages be delivered, even if they are
    * processed very quickly, may have a noticeable effect on the performance of
    * the page.
    *
    * Note that synthetic mouse events will be generated from touch events if
    * (and only if) you do not request touch events.
    *
    * When requesting input events through this function, the events will be
-   * delivered and <i>not</i> bubbled to the page. This means that even if you
-   * aren't interested in the message, no other parts of the page will get
-   * a crack at the message.
+   * delivered and <i>not</i> bubbled to the default handlers.
    *
    * <strong>Example:</strong>
    * @code
    *   RequestInputEvents(instance, PP_INPUTEVENT_CLASS_MOUSE);
    *   RequestFilteringInputEvents(instance,
    *       PP_INPUTEVENT_CLASS_WHEEL | PP_INPUTEVENT_CLASS_KEYBOARD);
    * @endcode
    *
    * @param instance The <code>PP_Instance</code> of the instance requesting
    * the given events.
@@ skipping 12 matching lines @@
    * events, these must use RequestFilteringInputEvents().
    */
   int32_t (*RequestInputEvents)(PP_Instance instance, uint32_t event_classes);
   /**
    * RequestFilteringInputEvents() requests that input events corresponding to
    * the given input events are delivered to the instance for filtering.
    *
    * By default, no input events are delivered. In most cases you would
    * register to receive events by calling RequestInputEvents(). In some cases,
    * however, you may wish to filter events such that they can be bubbled up
-   * to the DOM. In this case, register for those classes of events using
-   * this function instead of RequestInputEvents().
+   * to the default handlers. In this case, register for those classes of
+   * events using this function instead of RequestInputEvents().
    *
    * Filtering input events requires significantly more overhead than just
    * delivering them to the instance. As such, you should only request
    * filtering in those cases where it's absolutely necessary. The reason is
    * that it requires the browser to stop and block for the instance to handle
    * the input event, rather than sending the input event asynchronously. This
    * can have significant overhead.
    *
    * <strong>Example:</strong>
    * @code
@@ skipping 655 matching lines @@
   void (*GetSelection)(PP_Resource ime_event, uint32_t* start, uint32_t* end);
 };
 
 typedef struct PPB_IMEInputEvent_1_0 PPB_IMEInputEvent;
 /**
  * @}
  */
 
 #endif  /* PPAPI_C_PPB_INPUT_EVENT_H_ */