Improve the speech panel's performance

Improve the speech panel's performance

Currently, ChromeVox sends all queued speech output to the speech panel.

This unfortunately causes performance issues.

For example, in Gmail, if ChromeVox sends ~500 utterances, which can happen if we have a large block of text (since we split on sentences), ChromeVox stops responding to key commands.

ChromeVox should stay responsive in any situation especially if a user taps on the control key repeatedly.

This change makes it so we only show the currently spoken text which gets around the potentially expensive calls to send text to the panel background page (which blocks).

BUG=672955
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Committed: https://crrev.com/120bb61b5fd467ef232a893bd7b040fc208ee4c4
Cr-Commit-Position: refs/heads/master@{#438083}

[David Tseng, 2016-12-12 18:21:55]

Description was changed from

==========
Improve the speech panel's performance

Currently, ChromeVox sends all queued speech output to the speech panel.

This unfortunately causes performance issues.

For example, in Gmail, if ChromeVox sends ~500 utterances, which can happen if
we have a large block of text (since we split on sentences), ChromeVox stops
responding to key commands.

ChromeVox should stay responsive in any situation especially if a user taps on
the control key repeatedly.

This change makes it so we only show the currently spoken text which gets around
the potentially expensive calls to send text to the panel background page (which
blocks).

BUG=
==========

to

==========
Improve the speech panel's performance

Currently, ChromeVox sends all queued speech output to the speech panel.

This unfortunately causes performance issues.

For example, in Gmail, if ChromeVox sends ~500 utterances, which can happen if
we have a large block of text (since we split on sentences), ChromeVox stops
responding to key commands.

ChromeVox should stay responsive in any situation especially if a user taps on
the control key repeatedly.

This change makes it so we only show the currently spoken text which gets around
the potentially expensive calls to send text to the panel background page (which
blocks).

BUG=
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[David Tseng, 2016-12-12 18:22:13]

dtseng@chromium.org changed reviewers:
+ dmazzoni@chromium.org

[dmazzoni, 2016-12-12 18:36:15]

lgtm

[David Tseng, 2016-12-12 18:41:47]

Description was changed from

==========
Improve the speech panel's performance

Currently, ChromeVox sends all queued speech output to the speech panel.

This unfortunately causes performance issues.

For example, in Gmail, if ChromeVox sends ~500 utterances, which can happen if
we have a large block of text (since we split on sentences), ChromeVox stops
responding to key commands.

ChromeVox should stay responsive in any situation especially if a user taps on
the control key repeatedly.

This change makes it so we only show the currently spoken text which gets around
the potentially expensive calls to send text to the panel background page (which
blocks).

BUG=
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

to

==========
Improve the speech panel's performance

Currently, ChromeVox sends all queued speech output to the speech panel.

This unfortunately causes performance issues.

For example, in Gmail, if ChromeVox sends ~500 utterances, which can happen if
we have a large block of text (since we split on sentences), ChromeVox stops
responding to key commands.

ChromeVox should stay responsive in any situation especially if a user taps on
the control key repeatedly.

This change makes it so we only show the currently spoken text which gets around
the potentially expensive calls to send text to the panel background page (which
blocks).

BUG=672955
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[David Tseng, 2016-12-12 18:41:55]

The CQ bit was checked by dtseng@chromium.org

[commit-bot: I haz the power, 2016-12-12 18:42:36]

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-12-13 01:43:32]

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

[commit-bot: I haz the power, 2016-12-13 01:43:35]

Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[David Tseng, 2016-12-13 05:38:05]

The CQ bit was checked by dtseng@chromium.org

[commit-bot: I haz the power, 2016-12-13 05:38: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-12-13 06:27:00]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1481607485701810, "parent_rev":
"4d5149af9ebd507b9a141ece7e8babf9148575ff", "commit_rev":
"8007204efc34e4896e5d0fc38dfc5f4e0723ddb3"}

[commit-bot: I haz the power, 2016-12-13 06:27:32]

Description was changed from

==========
Improve the speech panel's performance

Currently, ChromeVox sends all queued speech output to the speech panel.

This unfortunately causes performance issues.

For example, in Gmail, if ChromeVox sends ~500 utterances, which can happen if
we have a large block of text (since we split on sentences), ChromeVox stops
responding to key commands.

ChromeVox should stay responsive in any situation especially if a user taps on
the control key repeatedly.

This change makes it so we only show the currently spoken text which gets around
the potentially expensive calls to send text to the panel background page (which
blocks).

BUG=672955
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

to

==========
Improve the speech panel's performance

Currently, ChromeVox sends all queued speech output to the speech panel.

This unfortunately causes performance issues.

For example, in Gmail, if ChromeVox sends ~500 utterances, which can happen if
we have a large block of text (since we split on sentences), ChromeVox stops
responding to key commands.

ChromeVox should stay responsive in any situation especially if a user taps on
the control key repeatedly.

This change makes it so we only show the currently spoken text which gets around
the potentially expensive calls to send text to the panel background page (which
blocks).

BUG=672955
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2570593002
==========

[commit-bot: I haz the power, 2016-12-13 06:27:34]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-13 06:30:08]

Description was changed from

==========
Improve the speech panel's performance

Currently, ChromeVox sends all queued speech output to the speech panel.

This unfortunately causes performance issues.

For example, in Gmail, if ChromeVox sends ~500 utterances, which can happen if
we have a large block of text (since we split on sentences), ChromeVox stops
responding to key commands.

ChromeVox should stay responsive in any situation especially if a user taps on
the control key repeatedly.

This change makes it so we only show the currently spoken text which gets around
the potentially expensive calls to send text to the panel background page (which
blocks).

BUG=672955
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2570593002
==========

to

==========
Improve the speech panel's performance

Currently, ChromeVox sends all queued speech output to the speech panel.

This unfortunately causes performance issues.

For example, in Gmail, if ChromeVox sends ~500 utterances, which can happen if
we have a large block of text (since we split on sentences), ChromeVox stops
responding to key commands.

ChromeVox should stay responsive in any situation especially if a user taps on
the control key repeatedly.

This change makes it so we only show the currently spoken text which gets around
the potentially expensive calls to send text to the panel background page (which
blocks).

BUG=672955
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Committed: https://crrev.com/120bb61b5fd467ef232a893bd7b040fc208ee4c4
Cr-Commit-Position: refs/heads/master@{#438083}
==========

[commit-bot: I haz the power, 2016-12-13 06:30:09]

Patchset 1 (id:??) landed as
https://crrev.com/120bb61b5fd467ef232a893bd7b040fc208ee4c4
Cr-Commit-Position: refs/heads/master@{#438083}