Add UseCounter for draggable attribute

Add UseCounter for draggable attribute

1. Both |draggable| and |-webkit-user-drag| mean the element with the attributes
  is dragged when user drags pointer:
2. |draggeble| is the HTML5 standard but |-webkit-user-drag| is not:
 https://w3c.github.io/html/editing.html#drag-and-drop
3. Thus we should deprecate |-webkit-user-drag| for interoperability.

However,  |-webkit-user-drag| is used 4% in wild. That's high to deprecate
immediately:
https://www.chromestatus.com/metrics/css/timeline/popularity/337

But if |draggable| is used higher than |-webkit-user-drag|, we can accelarate
that stream by deprecating |-webkit-user-drag|.

Committed: https://crrev.com/fa07c88ba5aced63585ab7b32d20a7aa3f18f66f
Cr-Commit-Position: refs/heads/master@{#415116}

[yoichio, 2016-08-10 09:34:35]

The CQ bit was checked by yoichio@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-10 09:34:55]

Dry run: 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-08-10 11:19:24]

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

[commit-bot: I haz the power, 2016-08-10 11:19:25]

Dry run: Try jobs failed on following builders:
  linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)

[yoichio, 2016-08-15 06:25:17]

Description was changed from

==========
draggable usecounter

BUG=
==========

to

==========
Add UseCounter for draggable attribute

I intend to deprecate -webkit-user-drag.

BUG=
==========

[yoichio, 2016-08-15 06:25:17]

yoichio@chromium.org changed reviewers:
+ tkent@chromium.org

[tkent, 2016-08-17 01:19:00]

> Add UseCounter for draggable attribute
>
> I intend to deprecate -webkit-user-drag.

I don't catch you.  Why do you count |draggable| content attribute to deprecate
|-webkit-user-drag| CSS property?

[yoichio, 2016-08-17 02:09:33]

On 2016/08/17 01:19:00, tkent wrote:
> > Add UseCounter for draggable attribute
> >
> > I intend to deprecate -webkit-user-drag.
> 
> I don't catch you.  Why do you count |draggable| content attribute to
deprecate
> |-webkit-user-drag| CSS property?

That's because 
1. Both |draggable| and |-webkit-user-drag| mean the element with the attributes

  is dragged when user drags pointer:
2. |draggeble| is the HTML5 standard but |-webkit-user-drag| is not:
 https://w3c.github.io/html/editing.html#drag-and-drop
3. Thus we should deprecate |-webkit-user-drag| for interoperability.

However,  |-webkit-user-drag| is used 4% in wild. That's high to deprecate
immediately:
https://www.chromestatus.com/metrics/css/timeline/popularity/337

But if |draggable| is used higher than |-webkit-user-drag|, we can accelarate
that
 stream by deprecating |-webkit-user-drag|.

[tkent, 2016-08-17 02:15:09]

On 2016/08/17 at 02:09:33, yoichio wrote:
> But if |draggable| is used higher than |-webkit-user-drag|, we can accelarate
that
>  stream by deprecating |-webkit-user-drag|.

ok, I understand.  lgtm

[yoichio, 2016-08-17 04:22:10]

Description was changed from

==========
Add UseCounter for draggable attribute

I intend to deprecate -webkit-user-drag.

BUG=
==========

to

==========
Add UseCounter for draggable attribute

1. Both |draggable| and |-webkit-user-drag| mean the element with the attributes
  is dragged when user drags pointer:
2. |draggeble| is the HTML5 standard but |-webkit-user-drag| is not:
 https://w3c.github.io/html/editing.html#drag-and-drop
3. Thus we should deprecate |-webkit-user-drag| for interoperability.

However,  |-webkit-user-drag| is used 4% in wild. That's high to deprecate
immediately:
https://www.chromestatus.com/metrics/css/timeline/popularity/337

But if |draggable| is used higher than |-webkit-user-drag|, we can accelarate
that stream by deprecating |-webkit-user-drag|.
==========

[yoichio, 2016-08-17 04:28:30]

yoichio@chromium.org changed reviewers:
+ mpearson@chromium.org

[yoichio, 2016-08-17 04:28:31]

mpearson@, could you review histograms.xml?

[Mark P, 2016-08-17 16:58:34]

histograms.xml lgtm

[yoichio, 2016-08-18 02:05:45]

The CQ bit was checked by yoichio@chromium.org

[commit-bot: I haz the power, 2016-08-18 02:06:25]

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-08-18 02:09:32]

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

[commit-bot: I haz the power, 2016-08-18 02:09:33]

Try jobs failed on following builders:
  mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[yoichio, 2016-08-23 04:28:10]

The CQ bit was checked by yoichio@chromium.org

[commit-bot: I haz the power, 2016-08-23 04:28:49]

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-08-23 04:31:58]

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

[commit-bot: I haz the power, 2016-08-23 04:31:59]

Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
  ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)

[yoichio, 2016-08-23 06:21:34]

The CQ bit was checked by yoichio@chromium.org

[yoichio, 2016-08-23 06:21:34]

The patchset sent to the CQ was uploaded after l-g-t-m from tkent@chromium.org,
mpearson@chromium.org
Link to the patchset: https://codereview.chromium.org/2234733002/#ps20001
(title: "rebase")

[commit-bot: I haz the power, 2016-08-23 06:21:57]

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-08-23 06:24:47]

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

[commit-bot: I haz the power, 2016-08-23 06:24:48]

Try jobs failed on following builders:
  mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)

[yoichio, 2016-08-24 04:53:11]

The CQ bit was checked by yoichio@chromium.org

[yoichio, 2016-08-24 04:53:12]

The patchset sent to the CQ was uploaded after l-g-t-m from tkent@chromium.org,
mpearson@chromium.org
Link to the patchset: https://codereview.chromium.org/2234733002/#ps40001
(title: "rebase")

[commit-bot: I haz the power, 2016-08-24 04:53:35]

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-08-24 06:40:08]

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

[commit-bot: I haz the power, 2016-08-24 06:40:09]

Try jobs failed on following builders:
  win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[yoichio, 2016-08-25 05:19:03]

The CQ bit was checked by yoichio@chromium.org

[yoichio, 2016-08-25 05:19:03]

The patchset sent to the CQ was uploaded after l-g-t-m from tkent@chromium.org,
mpearson@chromium.org
Link to the patchset: https://codereview.chromium.org/2234733002/#ps60001
(title: "rebase")

[commit-bot: I haz the power, 2016-08-25 05:19:26]

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-08-25 05:21:42]

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

[commit-bot: I haz the power, 2016-08-25 05:21:43]

Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
  ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[yoichio, 2016-08-25 07:42:26]

The CQ bit was checked by yoichio@chromium.org

[yoichio, 2016-08-25 07:42:27]

The patchset sent to the CQ was uploaded after l-g-t-m from tkent@chromium.org,
mpearson@chromium.org
Link to the patchset: https://codereview.chromium.org/2234733002/#ps80001
(title: "rebase")

[commit-bot: I haz the power, 2016-08-25 07:42:56]

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-08-25 09:39:09]

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

[commit-bot: I haz the power, 2016-08-25 09:39:10]

Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[yoichio, 2016-08-29 05:39:17]

The CQ bit was checked by yoichio@chromium.org

[yoichio, 2016-08-29 05:39:17]

The patchset sent to the CQ was uploaded after l-g-t-m from tkent@chromium.org,
mpearson@chromium.org
Link to the patchset: https://codereview.chromium.org/2234733002/#ps120001
(title: "rebase")

[commit-bot: I haz the power, 2016-08-29 05:39:39]

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-08-29 07:21:21]

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

[commit-bot: I haz the power, 2016-08-29 07:21:23]

Try jobs failed on following builders:
  linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)

[yoichio, 2016-08-30 01:56:27]

The CQ bit was checked by yoichio@chromium.org

[commit-bot: I haz the power, 2016-08-30 02:43:08]

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-08-30 04:49:11]

Description was changed from

==========
Add UseCounter for draggable attribute

1. Both |draggable| and |-webkit-user-drag| mean the element with the attributes
  is dragged when user drags pointer:
2. |draggeble| is the HTML5 standard but |-webkit-user-drag| is not:
 https://w3c.github.io/html/editing.html#drag-and-drop
3. Thus we should deprecate |-webkit-user-drag| for interoperability.

However,  |-webkit-user-drag| is used 4% in wild. That's high to deprecate
immediately:
https://www.chromestatus.com/metrics/css/timeline/popularity/337

But if |draggable| is used higher than |-webkit-user-drag|, we can accelarate
that stream by deprecating |-webkit-user-drag|.
==========

to

==========
Add UseCounter for draggable attribute

1. Both |draggable| and |-webkit-user-drag| mean the element with the attributes
  is dragged when user drags pointer:
2. |draggeble| is the HTML5 standard but |-webkit-user-drag| is not:
 https://w3c.github.io/html/editing.html#drag-and-drop
3. Thus we should deprecate |-webkit-user-drag| for interoperability.

However,  |-webkit-user-drag| is used 4% in wild. That's high to deprecate
immediately:
https://www.chromestatus.com/metrics/css/timeline/popularity/337

But if |draggable| is used higher than |-webkit-user-drag|, we can accelarate
that stream by deprecating |-webkit-user-drag|.
==========

[commit-bot: I haz the power, 2016-08-30 04:49:12]

Committed patchset #7 (id:120001)

[commit-bot: I haz the power, 2016-08-30 04:51:11]

Description was changed from

==========
Add UseCounter for draggable attribute

1. Both |draggable| and |-webkit-user-drag| mean the element with the attributes
  is dragged when user drags pointer:
2. |draggeble| is the HTML5 standard but |-webkit-user-drag| is not:
 https://w3c.github.io/html/editing.html#drag-and-drop
3. Thus we should deprecate |-webkit-user-drag| for interoperability.

However,  |-webkit-user-drag| is used 4% in wild. That's high to deprecate
immediately:
https://www.chromestatus.com/metrics/css/timeline/popularity/337

But if |draggable| is used higher than |-webkit-user-drag|, we can accelarate
that stream by deprecating |-webkit-user-drag|.
==========

to

==========
Add UseCounter for draggable attribute

1. Both |draggable| and |-webkit-user-drag| mean the element with the attributes
  is dragged when user drags pointer:
2. |draggeble| is the HTML5 standard but |-webkit-user-drag| is not:
 https://w3c.github.io/html/editing.html#drag-and-drop
3. Thus we should deprecate |-webkit-user-drag| for interoperability.

However,  |-webkit-user-drag| is used 4% in wild. That's high to deprecate
immediately:
https://www.chromestatus.com/metrics/css/timeline/popularity/337

But if |draggable| is used higher than |-webkit-user-drag|, we can accelarate
that stream by deprecating |-webkit-user-drag|.

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

[commit-bot: I haz the power, 2016-08-30 04:51:13]

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