Measure usage for Text.prototype.replaceWholeText()

Measure usage for Text.prototype.replaceWholeText()

Measure usage for Text.prototype.replaceWholeText() as it was removed
from DOM4:
http://www.w3.org/TR/2012/WD-dom-20121206/#text

This will allow us to determine if it can be deprecated / removed or
whether DOM4 needs to add it back.

Note that Firefox has already dropped support for this method. However,
IE10 still supports it.

R=arv
BUG=267521
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=155617

[arv (Not doing code reviews), 2013-08-05 13:26:39]

LGTM

[do-not-use, 2013-08-06 07:02:28]

On 2013/08/05 13:26:39, arv wrote:
> LGTM

tkent@, could you please take a look as well? Even though it is only a
deprecation for now, I think it still counts as a Web Exposed change.

[tkent, 2013-08-06 08:09:01]

On 2013/08/06 07:02:28, Christophe Dumez wrote:
> On 2013/08/05 13:26:39, arv wrote:
> > LGTM
> 
> tkent@, could you please take a look as well? Even though it is only a
> deprecation for now, I think it still counts as a Web Exposed change.

IMO, we should start with the second step in
http://www.chromium.org/blink#TOC-Launch-Process:-Deprecation, not the fourth
step.

[do-not-use, 2013-08-06 08:22:54]

On 2013/08/06 08:09:01, tkent wrote:
> On 2013/08/06 07:02:28, Christophe Dumez wrote:
> > On 2013/08/05 13:26:39, arv wrote:
> > > LGTM
> > 
> > tkent@, could you please take a look as well? Even though it is only a
> > deprecation for now, I think it still counts as a Web Exposed change.
> 
> IMO, we should start with the second step in
> http://www.chromium.org/blink#TOC-Launch-Process:-Deprecation, not the fourth
> step.

So use MeasureAs for now instead of DeprecateAs, right?

[tkent, 2013-08-06 08:28:19]

> So use MeasureAs for now instead of DeprecateAs, right?

Right.

[do-not-use, 2013-08-06 08:48:35]

On 2013/08/06 08:28:19, tkent wrote:
> > So use MeasureAs for now instead of DeprecateAs, right?
> 
> Right.

Ok, I updated the CL accordingly. I thought it would be OK to deprecate directly
considering Firefox already dropped its support. However, Taking the safer
approach cannot hurt.

[tkent, 2013-08-06 09:21:22]

lgtm

[commit-bot: I haz the power, 2013-08-06 09:49:06]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/ch.dumez@sisa.samsung.com/22182002/13001

[arv (Not doing code reviews), 2013-08-06 11:34:44]

This feature is not in Firefox and has been removed from the spec. I think
adding the deprecation warning directly makes sense.
On Aug 6, 2013 4:28 AM, <tkent@chromium.org> wrote:

> So use MeasureAs for now instead of DeprecateAs, right?
>>
>
> Right.
>
>
>
https://codereview.chromium.**org/22182002/<https://codereview.chromium.org/2...
>

[commit-bot: I haz the power, 2013-08-06 12:48:04]

Retried try job too often on mac_blink_rel for step(s) webkit_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac_blink_...

[commit-bot: I haz the power, 2013-08-06 15:25:11]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/ch.dumez@sisa.samsung.com/22182002/13001

[commit-bot: I haz the power, 2013-08-06 16:57:16]

Change committed as 155617

[do-not-use, 2013-08-06 17:37:13]

On 2013/08/06 11:34:44, arv wrote:
> This feature is not in Firefox and has been removed from the spec. I think
> adding the deprecation warning directly makes sense.
> On Aug 6, 2013 4:28 AM, <mailto:tkent@chromium.org> wrote:
> 
> > So use MeasureAs for now instead of DeprecateAs, right?
> >>
> >
> > Right.
> >
> >
> >
>
https://codereview.chromium.**org/22182002/%3Chttps://codereview.chromium.org...>
> >

Do you think I should send and "Intent to deprecate" email and see what other
think about it?

[arv (Not doing code reviews), 2013-08-06 18:12:44]

Personally I don't think it is needed but me and tkent clearly disagree and
he is an API owner so sending an email would probably be preferred.L
On Aug 6, 2013 1:37 PM, <ch.dumez@sisa.samsung.com> wrote:

> On 2013/08/06 11:34:44, arv wrote:
>
>> This feature is not in Firefox and has been removed from the spec. I think
>> adding the deprecation warning directly makes sense.
>> On Aug 6, 2013 4:28 AM, <mailto:tkent@chromium.org> wrote:
>>
>
>  > So use MeasureAs for now instead of DeprecateAs, right?
>> >>
>> >
>> > Right.
>> >
>> >
>> >
>>
>
> https://codereview.chromium.****org/22182002/%3Chttps://codere**
> view.chromium.org/22182002/ <http://codereview.chromium.org/22182002/>>
>
>> >
>>
>
> Do you think I should send and "Intent to deprecate" email and see what
> other
> think about it?
>
>
https://codereview.chromium.**org/22182002/<https://codereview.chromium.org/2...
>

[tkent, 2013-08-06 22:44:18]

On 2013/08/06 17:37:13, Christophe Dumez wrote:
> Do you think I should send and "Intent to deprecate" email and see what other
> think about it?

It should be sent when Chrome stable collects the UseCounter data and the
counter number proves the deprecation is reasonable.