[TTS] Cleanup a potential issue introduced in CL 2157793002

[TTS] Cleanup a potential issue introduced in CL 2157793002

Refactoring done in that CL looks like it could introduce potential problems
because now there's a path through the affected method that does not
reset the context.

This CL refactors the affected method to always reset the context while
preserving the refactoring done in 2157793002.

BUG=626770
Committed: https://crrev.com/e4fcb595ed939ec2f912d6fdd211ce70c73ee0ce
Cr-Commit-Position: refs/heads/master@{#421279}

[Donn Denman, 2016-09-26 23:42:36]

Description was changed from

==========
[TTS] Cleanup a potential issue introduced in CL 2157793002

Refactoring in done CL looks like it could introduce potential problems
because now there's a path through the affected method that does not
reset the context.

This CL refactors the affected method to always reset the context while
preserving the refactoring done in 2157793002.

BUG=626770
==========

to

==========
[TTS] Cleanup a potential issue introduced in CL 2157793002
    
Refactoring done in that CL looks like it could introduce potential problems
because now there's a path through the affected method that does not
reset the context.
    
This CL refactors the affected method to always reset the context while
preserving the refactoring done in 2157793002.
    
BUG=626770
==========

[Donn Denman, 2016-09-26 23:42:57]

donnd@chromium.org changed reviewers:
+ twellington@chromium.org

[Donn Denman, 2016-09-26 23:42:58]

Theresa, PTAL when convenient.

[Theresa, 2016-09-27 18:03:48]

The CQ bit was checked by twellington@chromium.org

[Theresa, 2016-09-27 18:03:49]

lgtm

[commit-bot: I haz the power, 2016-09-27 18:04:40]

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-27 18:40:04]

Description was changed from

==========
[TTS] Cleanup a potential issue introduced in CL 2157793002
    
Refactoring done in that CL looks like it could introduce potential problems
because now there's a path through the affected method that does not
reset the context.
    
This CL refactors the affected method to always reset the context while
preserving the refactoring done in 2157793002.
    
BUG=626770
==========

to

==========
[TTS] Cleanup a potential issue introduced in CL 2157793002
    
Refactoring done in that CL looks like it could introduce potential problems
because now there's a path through the affected method that does not
reset the context.
    
This CL refactors the affected method to always reset the context while
preserving the refactoring done in 2157793002.
    
BUG=626770
==========

[commit-bot: I haz the power, 2016-09-27 18:40:04]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-09-27 18:48:25]

Description was changed from

==========
[TTS] Cleanup a potential issue introduced in CL 2157793002
    
Refactoring done in that CL looks like it could introduce potential problems
because now there's a path through the affected method that does not
reset the context.
    
This CL refactors the affected method to always reset the context while
preserving the refactoring done in 2157793002.
    
BUG=626770
==========

to

==========
[TTS] Cleanup a potential issue introduced in CL 2157793002

Refactoring done in that CL looks like it could introduce potential problems
because now there's a path through the affected method that does not
reset the context.

This CL refactors the affected method to always reset the context while
preserving the refactoring done in 2157793002.

BUG=626770

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

[commit-bot: I haz the power, 2016-09-27 18:48:26]

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