Upstream version 7.36.149.0

[platform/framework/web/crosswalk.git] / src / native_client_sdk / doc_generated / pepper_dev / c / struct_p_p_b___input_event__1__0.html

diff --git a/src/native_client_sdk/doc_generated/pepper_dev/c/struct_p_p_b___input_event__1__0.html b/src/native_client_sdk/doc_generated/pepper_dev/c/struct_p_p_b___input_event__1__0.html
index d4739b9..8d02b57 100644 (file)
--- a/src/native_client_sdk/doc_generated/pepper_dev/c/struct_p_p_b___input_event__1__0.html
+++ b/src/native_client_sdk/doc_generated/pepper_dev/c/struct_p_p_b___input_event__1__0.html
@@ -138,7 +138,7 @@ Data Fields</h2><table class="memberdecls">
 </div>
 <div class="memdoc">
 <p><a class="el" href="struct_p_p_b___input_event__1__0.html#a42dcc8edf80141680e919258f3066069" title="RequestFilteringInputEvents() requests that input events corresponding to the given input events are ...">RequestFilteringInputEvents()</a> requests that input events corresponding to the given input events are delivered to the instance for filtering. </p>
-<p>By default, no input events are delivered. In most cases you would register to receive events by calling <a class="el" href="struct_p_p_b___input_event__1__0.html#a369d79730ad84d0b8dee9127c114086e" title="RequestInputEvent() requests that input events corresponding to the given input events are delivered ...">RequestInputEvents()</a>. 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 <a class="el" href="struct_p_p_b___input_event__1__0.html#a369d79730ad84d0b8dee9127c114086e" title="RequestInputEvent() requests that input events corresponding to the given input events are delivered ...">RequestInputEvents()</a>.</p>
+<p>By default, no input events are delivered. In most cases you would register to receive events by calling <a class="el" href="struct_p_p_b___input_event__1__0.html#a369d79730ad84d0b8dee9127c114086e" title="RequestInputEvent() requests that input events corresponding to the given input events are delivered ...">RequestInputEvents()</a>. In some cases, however, you may wish to filter events such that they can be bubbled up to the default handlers. In this case, register for those classes of events using this function instead of <a class="el" href="struct_p_p_b___input_event__1__0.html#a369d79730ad84d0b8dee9127c114086e" title="RequestInputEvent() requests that input events corresponding to the given input events are delivered ...">RequestInputEvents()</a>.</p>
 <p>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.</p>
 <p><b>Example:</b> </p>
 <div class="fragment"><pre class="fragment">   <a class="code" href="struct_p_p_b___input_event__1__0.html#a369d79730ad84d0b8dee9127c114086e" title="RequestInputEvent() requests that input events corresponding to the given input events are delivered ...">RequestInputEvents</a>(instance, <a class="code" href="group___enums.html#ggafe68e3c1031daa4a6496845ff47649cda79ccc5180eb39c52ab3207f0c876dd52" title="Request mouse input events.">PP_INPUTEVENT_CLASS_MOUSE</a>);
@@ -162,7 +162,7 @@ Data Fields</h2><table class="memberdecls">
 <p>By default, no input events are delivered. Call this function with the classes of events you are interested in to have them be delivered to the instance. Calling this function will override any previous setting for each specified class of input events (for example, if you previously called <a class="el" href="struct_p_p_b___input_event__1__0.html#a42dcc8edf80141680e919258f3066069" title="RequestFilteringInputEvents() requests that input events corresponding to the given input events are ...">RequestFilteringInputEvents()</a>, this function will set those events to non-filtering mode).</p>
 <p>Input events may have high overhead, so you should only request input events that your plugin will actually handle. For example, the browser may 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.</p>
 <p>Note that synthetic mouse events will be generated from touch events if (and only if) you do not request touch events.</p>
-<p>When requesting input events through this function, the events will be delivered and <em>not</em> 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.</p>
+<p>When requesting input events through this function, the events will be delivered and <em>not</em> bubbled to the default handlers.</p>
 <p><b>Example:</b> </p>
 <div class="fragment"><pre class="fragment">   <a class="code" href="struct_p_p_b___input_event__1__0.html#a369d79730ad84d0b8dee9127c114086e" title="RequestInputEvent() requests that input events corresponding to the given input events are delivered ...">RequestInputEvents</a>(instance, <a class="code" href="group___enums.html#ggafe68e3c1031daa4a6496845ff47649cda79ccc5180eb39c52ab3207f0c876dd52" title="Request mouse input events.">PP_INPUTEVENT_CLASS_MOUSE</a>);
    <a class="code" href="struct_p_p_b___input_event__1__0.html#a42dcc8edf80141680e919258f3066069" title="RequestFilteringInputEvents() requests that input events corresponding to the given input events are ...">RequestFilteringInputEvents</a>(instance,