Don't process more than the queued events during rAF.

Don't process more than the queued events during rAF.

There was potential that a stream events could enter rAF while it was being
processed. This was an initial design consideration but after talking with
an external partner it appears that probably we should just process what
is queued. This gives the benefit that only one type of a given event
will be processed during the callback.

BUG=625693
Committed: https://crrev.com/ed255334e459137808c04ede96e8a3253ca3dde5
Cr-Commit-Position: refs/heads/master@{#418618}

[dtapuska, 2016-09-14 14:56:54]

The CQ bit was checked by dtapuska@chromium.org to run a CQ dry run

[dtapuska, 2016-09-14 14:57:01]

Description was changed from

==========
Don't process more than the queued events during rAF.

There was potential that a stream events could enter rAF while it was being
processed. This was an initial design consideration but after talking with
an external partner it appears that probably we should just process what
is queued. This gives the benefit that only one type of a given event
will be processed during the callback.

BUG=625693
==========

to

==========
Don't process more than the queued events during rAF.

There was potential that a stream events could enter rAF while it was being
processed. This was an initial design consideration but after talking with
an external partner it appears that probably we should just process what
is queued. This gives the benefit that only one type of a given event
will be processed during the callback.

BUG=625693
==========

[dtapuska, 2016-09-14 14:57:01]

dtapuska@chromium.org changed reviewers:
+ tdresser@chromium.org

[commit-bot: I haz the power, 2016-09-14 14:57:24]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-14 16:03:13]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-14 16:03:14]

Dry run: This issue passed the CQ dry run.

[tdresser, 2016-09-14 16:33:26]

LGTM

https://codereview.chromium.org/2342603003/diff/1/content/renderer/input/main...
File content/renderer/input/main_thread_event_queue.cc (right):

https://codereview.chromium.org/2342603003/diff/1/content/renderer/input/main...
content/renderer/input/main_thread_event_queue.cc:240:
in_flight_event_.reset(events_to_process.front().release());
Can we use 
in_flight_event_ = std::move(events_to_process.front);
?

[dtapuska, 2016-09-14 17:19:32]

https://codereview.chromium.org/2342603003/diff/1/content/renderer/input/main...
File content/renderer/input/main_thread_event_queue.cc (right):

https://codereview.chromium.org/2342603003/diff/1/content/renderer/input/main...
content/renderer/input/main_thread_event_queue.cc:240:
in_flight_event_.reset(events_to_process.front().release());
On 2016/09/14 16:33:26, tdresser wrote:
> Can we use 
> in_flight_event_ = std::move(events_to_process.front);
> ?

Done.

[dtapuska, 2016-09-14 17:19:48]

The CQ bit was checked by dtapuska@chromium.org

[dtapuska, 2016-09-14 17:19:54]

The patchset sent to the CQ was uploaded after l-g-t-m from
tdresser@chromium.org
Link to the patchset: https://codereview.chromium.org/2342603003/#ps20001
(title: "Fix nit")

[commit-bot: I haz the power, 2016-09-14 17:20:29]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-14 18:34:12]

Description was changed from

==========
Don't process more than the queued events during rAF.

There was potential that a stream events could enter rAF while it was being
processed. This was an initial design consideration but after talking with
an external partner it appears that probably we should just process what
is queued. This gives the benefit that only one type of a given event
will be processed during the callback.

BUG=625693
==========

to

==========
Don't process more than the queued events during rAF.

There was potential that a stream events could enter rAF while it was being
processed. This was an initial design consideration but after talking with
an external partner it appears that probably we should just process what
is queued. This gives the benefit that only one type of a given event
will be processed during the callback.

BUG=625693
==========

[commit-bot: I haz the power, 2016-09-14 18:34:13]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-09-14 18:36:30]

Description was changed from

==========
Don't process more than the queued events during rAF.

There was potential that a stream events could enter rAF while it was being
processed. This was an initial design consideration but after talking with
an external partner it appears that probably we should just process what
is queued. This gives the benefit that only one type of a given event
will be processed during the callback.

BUG=625693
==========

to

==========
Don't process more than the queued events during rAF.

There was potential that a stream events could enter rAF while it was being
processed. This was an initial design consideration but after talking with
an external partner it appears that probably we should just process what
is queued. This gives the benefit that only one type of a given event
will be processed during the callback.

BUG=625693

Committed: https://crrev.com/ed255334e459137808c04ede96e8a3253ca3dde5
Cr-Commit-Position: refs/heads/master@{#418618}
==========

[commit-bot: I haz the power, 2016-09-14 18:36:32]

Patchset 2 (id:??) landed as
https://crrev.com/ed255334e459137808c04ede96e8a3253ca3dde5
Cr-Commit-Position: refs/heads/master@{#418618}