Pepper: Fix comments for PPB and PPP InputEvent.

ppapi/api/ppp_input_event.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.
  */
 
 /**
  * This file defines the API for receiving input events from the browser.
  */
 
 label Chrome {
   M14 = 0.1
 };
 
 [version=0.1, macro="PPP_INPUT_EVENT_INTERFACE"]
 interface PPP_InputEvent {
   /**
    * Function for receiving input events from the browser.
    *
    * In order to receive input events, you must register for them by calling
    * PPB_InputEvent.RequestInputEvents() or RequestFilteringInputEvents(). By
    * default, no events are delivered.
    *
-   * If the event was handled, it will not be forwarded to the web page or
-   * browser. If it was not handled, it will bubble according to the normal
-   * rules. So it is important that an instance respond accurately with whether
-   * event propagation should continue.
+   * If the event was handled, it will not be forwarded to the default handlers
+   * in the web page.  If it was not handled, it may be dispatched to a default
+   * handler. So it is important that an instance respond accurately with
+   * whether event propagation should continue.
    *
    * Event propagation also controls focus. If you handle an event like a mouse
    * event, typically the instance will be given focus. Returning false from
    * a filtered event handler or not registering for an event type means that
    * the click will be given to a lower part of the page and your instance will
    * not receive focus. This allows an instance to be partially transparent,
    * where clicks on the transparent areas will behave like clicks to the
    * underlying page.
    *
    * In general, you should try to keep input event handling short. Especially
@@ skipping 17 matching lines @@
    * @return PP_TRUE if the event was handled, PP_FALSE if not. If you have
    * registered to filter this class of events by calling
    * RequestFilteringInputEvents, and you return PP_FALSE, the event will
    * be forwarded to the page (and eventually the browser) for the default
    * handling. For non-filtered events, the return value will be ignored.
    */
   PP_Bool HandleInputEvent([in] PP_Instance instance,
                            [in] PP_Resource input_event);
 };