Measure current usage statistics for MediaStream label and stop() before going for deprecation.

Measure current usage statistics for MediaStream label and stop() before going for deprecation.
As per spec, both label and stop have been deprecated.
Spec = http://dev.w3.org/2011/webrtc/editor/getusermedia.html#mediastream

BUG=407039
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=182408

[Vinod Keshav, 2014-09-03 09:40:12]

v.keshav@samsung.com changed reviewers:
+ abarth@chromium.org, grunell@chromium.org

[Vinod Keshav, 2014-09-03 09:40:36]

PTAL

[Henrik Grunell, 2014-09-04 08:20:29]

LGTM.

Just FTR, label and id are the same (renamed). Removing label will finalize the
renaming.

[Vinod Keshav, 2014-09-10 09:49:06]

On 2014/09/04 08:20:29, Henrik Grunell wrote:
> LGTM.
> 
> Just FTR, label and id are the same (renamed). Removing label will finalize
the
> renaming.

abarth@ ping

[Vinod Keshav, 2014-09-16 02:57:19]

On 2014/09/10 09:49:06, Vinod Keshav wrote:
> On 2014/09/04 08:20:29, Henrik Grunell wrote:
> > LGTM.
> > 
> > Just FTR, label and id are the same (renamed). Removing label will finalize
> the
> > renaming.
> 
> abarth@ ping

abarth@, can you please take a look. Thanks.

[Vinod Keshav, 2014-09-22 07:19:39]

v.keshav@samsung.com changed reviewers:
+ haraken@chromium.org

[Vinod Keshav, 2014-09-22 07:19:40]

haraken@ PTAL

[haraken, 2014-09-22 08:04:15]

Just to confirm: You want to use [MeasureAs], not [DeprecateAs]?

[Vinod Keshav, 2014-09-22 08:18:14]

On 2014/09/22 08:04:15, haraken wrote:
> Just to confirm: You want to use [MeasureAs], not [DeprecateAs]?

yes, that's right. What to first measure and then deprecate.

[haraken, 2014-09-22 08:19:29]

LGTM

[Vinod Keshav, 2014-09-22 08:45:00]

The CQ bit was checked by v.keshav@samsung.com

[commit-bot: I haz the power, 2014-09-22 08:45:47]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/535733005/1

[commit-bot: I haz the power, 2014-09-22 08:45:54]

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

[commit-bot: I haz the power, 2014-09-22 08:45:55]

Failed to apply patch for Source/core/frame/UseCounter.h:
While running patch -p1 --forward --force --no-backup-if-mismatch;
  patching file Source/core/frame/UseCounter.h
  Hunk #1 FAILED at 495.
  1 out of 1 hunk FAILED -- saving rejects to file
Source/core/frame/UseCounter.h.rej

Patch:       Source/core/frame/UseCounter.h
Index: Source/core/frame/UseCounter.h
diff --git a/Source/core/frame/UseCounter.h b/Source/core/frame/UseCounter.h
index
515f3f6b60377ec46d56d884f7f56e7db88f767e..ca1d77023b4539260cde76e8ccf185f483c0c53d
100644
--- a/Source/core/frame/UseCounter.h
+++ b/Source/core/frame/UseCounter.h
@@ -495,6 +495,8 @@ public:
         SrcsetWDescriptor = 524,
         SelectionContainsNode = 525,
         MediaStreamEnded = 526,
+        MediaStreamLabel = 527,
+        MediaStreamStop = 528,
         // Add new features immediately above this line. Don't change assigned
         // numbers of any item, and don't reuse removed slots.
         // Also, run update_use_counter_feature_enum.py in
chromium/src/tools/metrics/histograms/

[Vinod Keshav, 2014-09-22 09:33:29]

The CQ bit was checked by v.keshav@samsung.com

[Vinod Keshav, 2014-09-22 09:33:40]

The CQ bit was unchecked by v.keshav@samsung.com

[Vinod Keshav, 2014-09-22 09:33:54]

The CQ bit was checked by v.keshav@samsung.com

[commit-bot: I haz the power, 2014-09-22 09:34:24]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/535733005/20001

[commit-bot: I haz the power, 2014-09-22 11:19:58]

Committed patchset #2 (id:20001) as 182408

[Erik Corry, 2014-10-01 13:59:24]

erik.corry@gmail.com changed reviewers:
+ erik.corry@gmail.com

[Erik Corry, 2014-10-01 13:59:25]

It seems the corresponding change was not done on the Chromium tools side, or
perhaps I am missing something. See https://codereview.chromium.org/622543003

[Henrik Grunell, 2014-10-03 07:54:40]

On 2014/10/01 13:59:25, Erik Corry wrote:
> It seems the corresponding change was not done on the Chromium tools side, or
> perhaps I am missing something. See https://codereview.chromium.org/622543003

You're right that it's missing. In fact, I hadn't thought of the Chromium change
(not mentioned in
http://www.chromium.org/blink#TOC-Web-Platform-Changes:-Process). But now it's
obvious, Thanks.