Remove use counters for Element methods that have been settled in spec

Remove use counters for Element methods that have been settled in spec

https://dom.spec.whatwg.org/#interface-element

This also moves the non-spec'd webkitMatchesSelector,
insertAdjacentElement and insertAdjacentText.

The use counter for webkitMatchesSelector is left in place, because it
it's somewhat interesting to follow its decline. The usage ought to be
dominated by old versions of jQuery and other libraries, and so it says
something about how long it takes for those libraries to be dropped or
upgraded in the wild. jQuery and other libraries were updated around the
time that the unprefixed matches was shipped in Blink, and usage of
webkitMatchesSelector has roughly halved every year since. (Since it's
now implemented in all engines, it's still unlikely to ever be removed.)

Original commits:
https://crrev.com/d92494c5c13990d8ab8d8cd73b0a20b8b2dee1e9
https://crrev.com/a706ad3cd488d6827cfcc99cd67cc30625296928
https://crrev.com/709823c231eb406d6928938c745effb16d6b3b3c
https://crrev.com/45b5b0427c403ba30d0067921b2639a31f0190df
https://crrev.com/6bcc2fb1c405cca7971ef6f361d94f8e8c63e726

BUG=460722
Committed: https://crrev.com/5e2a7d4d2ade23509e4e00464736556db8eff59d
Cr-Commit-Position: refs/heads/master@{#381701}

[philipj_slow, 2016-03-16 10:30:46]

The CQ bit was checked by philipj@opera.com to run a CQ dry run

[commit-bot: I haz the power, 2016-03-16 10:31:03]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1804383002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1804383002/1

[philipj_slow, 2016-03-16 11:02:49]

philipj@opera.com changed reviewers:
+ ojan@chromium.org, tkent@chromium.org

[philipj_slow, 2016-03-16 11:02:49]

tkent@, ojan@, you reviewed some of the original CLs.

My thinking here is that when the counters have served their original purpose
and we don't think any future decisions could depend on them, we should just as
well remove them to git rid of the (very small) overhead that they add.

[commit-bot: I haz the power, 2016-03-16 13:16:39]

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

[commit-bot: I haz the power, 2016-03-16 13:16:40]

Dry run: This issue passed the CQ dry run.

[tkent, 2016-03-16 23:57:46]

lgtm

https://codereview.chromium.org/1804383002/diff/1/third_party/WebKit/Source/c...
File third_party/WebKit/Source/core/dom/Element.idl (right):

https://codereview.chromium.org/1804383002/diff/1/third_party/WebKit/Source/c...
third_party/WebKit/Source/core/dom/Element.idl:61: [RaisesException,
ImplementedAs=matches] boolean webkitMatchesSelector(DOMString selectors); //
historical alias of .matches
Won't we discuss removing webkitMatchesSelector from the specification in the
future?

[philipj_slow, 2016-03-17 10:41:42]

https://codereview.chromium.org/1804383002/diff/1/third_party/WebKit/Source/c...
File third_party/WebKit/Source/core/dom/Element.idl (right):

https://codereview.chromium.org/1804383002/diff/1/third_party/WebKit/Source/c...
third_party/WebKit/Source/core/dom/Element.idl:61: [RaisesException,
ImplementedAs=matches] boolean webkitMatchesSelector(DOMString selectors); //
historical alias of .matches
On 2016/03/16 23:57:45, tkent wrote:
> Won't we discuss removing webkitMatchesSelector from the specification in the
> future?

Usage is now about 10%, and has for far roughly halved every year. If this
continues it will be ~0.01% in 10 years. By that time I think it's very unlikely
that anyone would bother removing an alias that has already been supported
interoperably for 10 years, at least I would argue against it.

But, I did hesitate about removing this counter because it could be interesting
to follow how usage drop over time. Because it's likely dominated by jQuery and
other libraries, it's a proxy for how old versions of these libraries decrease
over time. So I'll put the use counter back.

[philipj_slow, 2016-03-17 10:48:17]

Description was changed from

==========
Remove use counters for Element methods that have been settled in spec

https://dom.spec.whatwg.org/#interface-element

This also moves the non-spec'd webkitMatchesSelector,
insertAdjacentElement and insertAdjacentText.

Original commits:
https://crrev.com/d92494c5c13990d8ab8d8cd73b0a20b8b2dee1e9
https://crrev.com/a706ad3cd488d6827cfcc99cd67cc30625296928
https://crrev.com/709823c231eb406d6928938c745effb16d6b3b3c
https://crrev.com/45b5b0427c403ba30d0067921b2639a31f0190df
https://crrev.com/f9ee96f1699357da3e00f77e6b669fb6f9ea2948
https://crrev.com/6bcc2fb1c405cca7971ef6f361d94f8e8c63e726

BUG=460722
==========

to

==========
Remove use counters for Element methods that have been settled in spec

https://dom.spec.whatwg.org/#interface-element

This also moves the non-spec'd webkitMatchesSelector,
insertAdjacentElement and insertAdjacentText.

The use counter for webkitMatchesSelector is left in place, because it
it's somewhat interesting to follow its decline. The usage ought to be
dominated by old versions of jQuery and other libraries, and so it says
something about how long it takes for those libraries to be dropped or
upgraded in the wild. jQuery and other libraries were updated around the
time that the unprefixed matches was shipped in Blink, and usage of
webkitMatchesSelector has roughly halved every year since. (Since it's
now implemented in all engines, it's still unlikely to ever be removed.)

Original commits:
https://crrev.com/d92494c5c13990d8ab8d8cd73b0a20b8b2dee1e9
https://crrev.com/a706ad3cd488d6827cfcc99cd67cc30625296928
https://crrev.com/709823c231eb406d6928938c745effb16d6b3b3c
https://crrev.com/45b5b0427c403ba30d0067921b2639a31f0190df
https://crrev.com/6bcc2fb1c405cca7971ef6f361d94f8e8c63e726

BUG=460722
==========

[philipj_slow, 2016-03-17 10:52:12]

The CQ bit was checked by philipj@opera.com

[philipj_slow, 2016-03-17 10:52:12]

The patchset sent to the CQ was uploaded after l-g-t-m from tkent@chromium.org
Link to the patchset: https://codereview.chromium.org/1804383002/#ps20001
(title: "keep counting webkitMatchesSelector")

[commit-bot: I haz the power, 2016-03-17 10:52:26]

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

[commit-bot: I haz the power, 2016-03-17 13:28:05]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-03-17 13:29:36]

Description was changed from

==========
Remove use counters for Element methods that have been settled in spec

https://dom.spec.whatwg.org/#interface-element

This also moves the non-spec'd webkitMatchesSelector,
insertAdjacentElement and insertAdjacentText.

The use counter for webkitMatchesSelector is left in place, because it
it's somewhat interesting to follow its decline. The usage ought to be
dominated by old versions of jQuery and other libraries, and so it says
something about how long it takes for those libraries to be dropped or
upgraded in the wild. jQuery and other libraries were updated around the
time that the unprefixed matches was shipped in Blink, and usage of
webkitMatchesSelector has roughly halved every year since. (Since it's
now implemented in all engines, it's still unlikely to ever be removed.)

Original commits:
https://crrev.com/d92494c5c13990d8ab8d8cd73b0a20b8b2dee1e9
https://crrev.com/a706ad3cd488d6827cfcc99cd67cc30625296928
https://crrev.com/709823c231eb406d6928938c745effb16d6b3b3c
https://crrev.com/45b5b0427c403ba30d0067921b2639a31f0190df
https://crrev.com/6bcc2fb1c405cca7971ef6f361d94f8e8c63e726

BUG=460722
==========

to

==========
Remove use counters for Element methods that have been settled in spec

https://dom.spec.whatwg.org/#interface-element

This also moves the non-spec'd webkitMatchesSelector,
insertAdjacentElement and insertAdjacentText.

The use counter for webkitMatchesSelector is left in place, because it
it's somewhat interesting to follow its decline. The usage ought to be
dominated by old versions of jQuery and other libraries, and so it says
something about how long it takes for those libraries to be dropped or
upgraded in the wild. jQuery and other libraries were updated around the
time that the unprefixed matches was shipped in Blink, and usage of
webkitMatchesSelector has roughly halved every year since. (Since it's
now implemented in all engines, it's still unlikely to ever be removed.)

Original commits:
https://crrev.com/d92494c5c13990d8ab8d8cd73b0a20b8b2dee1e9
https://crrev.com/a706ad3cd488d6827cfcc99cd67cc30625296928
https://crrev.com/709823c231eb406d6928938c745effb16d6b3b3c
https://crrev.com/45b5b0427c403ba30d0067921b2639a31f0190df
https://crrev.com/6bcc2fb1c405cca7971ef6f361d94f8e8c63e726

BUG=460722

Committed: https://crrev.com/5e2a7d4d2ade23509e4e00464736556db8eff59d
Cr-Commit-Position: refs/heads/master@{#381701}
==========

[commit-bot: I haz the power, 2016-03-17 13:29:37]

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