Fix remote trace recording via chrome://inspect?tracing

Fix remote trace recording via chrome://inspect?tracing

This was regressed in two different places, first by
https://codereview.chromium.org/2515903002
and then by
https://codereview.chromium.org/2607833002

BUG=680170

[caseq, 2017-01-12 00:48:20]

caseq@chromium.org changed reviewers:
+ dgozman@chromium.org, pfeldman@chromium.org

[pfeldman, 2017-01-12 01:11:04]

lgtm

[caseq, 2017-01-12 01:15:25]

The CQ bit was checked by caseq@chromium.org

[commit-bot: I haz the power, 2017-01-12 01:16:02]

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, 2017-01-12 02:31:43]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1484183725219070,
"parent_rev": "1916748e2f13a9f80080d010a9adc6ba74028a59", "commit_rev":
"3a06f2645235a7de84376c6615553957e49d0563"}

[commit-bot: I haz the power, 2017-01-12 02:41:03]

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

[commit-bot: I haz the power, 2017-01-12 02:41:04]

Prior attempt to commit was detected, but we were not able to check whether the
issue was successfully committed. Please check Git history manually and re-check
CQ or close this issue as needed.

[pfeldman, 2017-02-23 01:18:27]

Description was changed from

==========
Fix remote trace recording via chrome://inspect?tracing

This was regressed in two different places, first by
https://codereview.chromium.org/2515903002
and then by
https://codereview.chromium.org/2607833002

BUG=680170
==========

to

==========
Fix remote trace recording via chrome://inspect?tracing

This was regressed in two different places, first by
https://codereview.chromium.org/2515903002
and then by
https://codereview.chromium.org/2607833002

BUG=680170
==========