Add constructor for DataTransfer

Add constructor for DataTransfer

This is being added to support the Asynchronous Clipboard API, which
requires a DataTransfer object to store the data for the write() operation.

DataTransfer:
Intent to Implement & Ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/NY8OPSzHGuE
WHATWG HTML spec bug: https://github.com/whatwg/html/issues/2190
Spec: https://html.spec.whatwg.org/multipage/interaction.html#the-datatransfer-interface
W3C WebPlatformTest PR: https://github.com/w3c/web-platform-tests/pull/5232

Async Clipboard:
W3C Spec: https://w3c.github.io/clipboard-apis/#async-clipboard-api

BUG=677564
Review-Url: https://codereview.chromium.org/2784473003
Cr-Commit-Position: refs/heads/master@{#461281}
Committed: https://chromium.googlesource.com/chromium/src/+/1f2f12faf6b42983525f917bd5fabc2f02bdf8a3

[garykac, 2017-03-28 22:31:08]

garykac@chromium.org changed reviewers:
+ rbyers@chromium.org

[Rick Byers, 2017-03-29 17:47:53]

Description was changed from

==========
Add constructor for DataTransfer

This is being added to support the Asynchronous Clipboard API, which
requires a DataTransfer object to store the data for the write() operation.

DataTransfer:
WHATWG HTML spec bug: https://github.com/whatwg/html/issues/2190
W3C WebPlatformTest PR: https://github.com/w3c/web-platform-tests/pull/5232

Async Clipboard:
W3C Spec: https://w3c.github.io/clipboard-apis/#async-clipboard-api

BUG=677564
==========

to

==========
Add constructor for DataTransfer

This is being added to support the Asynchronous Clipboard API, which
requires a DataTransfer object to store the data for the write() operation.

DataTransfer:
WHATWG HTML spec bug: https://github.com/whatwg/html/issues/2190
Spec:
https://html.spec.whatwg.org/multipage/interaction.html#the-datatransfer-inte...
W3C WebPlatformTest PR: https://github.com/w3c/web-platform-tests/pull/5232

Async Clipboard:
W3C Spec: https://w3c.github.io/clipboard-apis/#async-clipboard-api

BUG=677564
==========

[Rick Byers, 2017-03-29 17:49:20]

Change looks good, thanks.  I added a link to the spec for this too since it's
landed already.  But there hasn't been an "intent-to-ship" yet, right?  I think
this CL will fail virtual/stable/webexposed tests as a result.

You can either put this behind a status=experimental RuntimeEnabledFeature for
now, or just send your intent-to-ship before landing (I don't expect it to be
controversial).

[garykac, 2017-03-29 20:05:03]

On 2017/03/29 17:49:20, Rick Byers wrote:
> Change looks good, thanks.  I added a link to the spec for this too since it's
> landed already.  But there hasn't been an "intent-to-ship" yet, right?  I
think
> this CL will fail virtual/stable/webexposed tests as a result.

I hadn't considered that -- I assumed this would be covered by the clipboard
intent.

But now that you'd pointed it out, it makes sense to break this out.

> You can either put this behind a status=experimental RuntimeEnabledFeature for
> now, or just send your intent-to-ship before landing (I don't expect it to be
> controversial).

I'll send the intent now.

[garykac, 2017-03-29 21:26:31]

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

[commit-bot: I haz the power, 2017-03-29 21:27:40]

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, 2017-03-29 22:48:58]

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

[commit-bot: I haz the power, 2017-03-29 22:48:59]

Dry run: Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[garykac, 2017-03-30 00:52:18]

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

[commit-bot: I haz the power, 2017-03-30 00:53:05]

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, 2017-03-30 02:44:02]

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

[commit-bot: I haz the power, 2017-03-30 02:44:03]

Dry run: 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_...)

[garykac, 2017-03-30 17:06:00]

On 2017/03/29 20:05:03, garykac wrote:
> On 2017/03/29 17:49:20, Rick Byers wrote:
> > Change looks good, thanks.  I added a link to the spec for this too since
it's
> > landed already.  But there hasn't been an "intent-to-ship" yet, right?  I
> think
> > this CL will fail virtual/stable/webexposed tests as a result.
> 
> I hadn't considered that -- I assumed this would be covered by the clipboard
> intent.
> 
> But now that you'd pointed it out, it makes sense to break this out.
> 
> > You can either put this behind a status=experimental RuntimeEnabledFeature
for
> > now, or just send your intent-to-ship before landing (I don't expect it to
be
> > controversial).
> 
> I'll send the intent now.

Intent sent:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/NY8OPSzHGuE

[garykac, 2017-03-30 20:39:14]

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

[commit-bot: I haz the power, 2017-03-30 20:40:34]

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, 2017-03-30 23:30:28]

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

[commit-bot: I haz the power, 2017-03-30 23:30:29]

Dry run: Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Rick Byers, 2017-03-31 20:55:54]

LGTM now that there's an approved intent-to-ship.  Please add the link to that
thread in the CL description.

[Rick Byers, 2017-03-31 20:55:56]

LGTM now that there's an approved intent-to-ship.  Please add the link to that
thread in the CL description.

[garykac, 2017-03-31 20:56:56]

Description was changed from

==========
Add constructor for DataTransfer

This is being added to support the Asynchronous Clipboard API, which
requires a DataTransfer object to store the data for the write() operation.

DataTransfer:
WHATWG HTML spec bug: https://github.com/whatwg/html/issues/2190
Spec:
https://html.spec.whatwg.org/multipage/interaction.html#the-datatransfer-inte...
W3C WebPlatformTest PR: https://github.com/w3c/web-platform-tests/pull/5232

Async Clipboard:
W3C Spec: https://w3c.github.io/clipboard-apis/#async-clipboard-api

BUG=677564
==========

to

==========
Add constructor for DataTransfer

This is being added to support the Asynchronous Clipboard API, which
requires a DataTransfer object to store the data for the write() operation.

DataTransfer:
Intent to Implement & Ship:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/NY8OPSzHGuE
WHATWG HTML spec bug: https://github.com/whatwg/html/issues/2190
Spec:
https://html.spec.whatwg.org/multipage/interaction.html#the-datatransfer-inte...
W3C WebPlatformTest PR: https://github.com/w3c/web-platform-tests/pull/5232

Async Clipboard:
W3C Spec: https://w3c.github.io/clipboard-apis/#async-clipboard-api

BUG=677564
==========

[garykac, 2017-03-31 20:57:10]

On 2017/03/31 20:55:56, Rick Byers wrote:
> LGTM now that there's an approved intent-to-ship.  Please add the link to that
> thread in the CL description.

Done.

[garykac, 2017-03-31 20:57:15]

The CQ bit was checked by garykac@chromium.org

[commit-bot: I haz the power, 2017-03-31 20:57:52]

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-04-01 00:09:09]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1490993835655330,
"parent_rev": "600e4f21b281216ddd57b3644a44ffe7471a67d2", "commit_rev":
"1f2f12faf6b42983525f917bd5fabc2f02bdf8a3"}

[commit-bot: I haz the power, 2017-04-01 00:10:37]

Description was changed from

==========
Add constructor for DataTransfer

This is being added to support the Asynchronous Clipboard API, which
requires a DataTransfer object to store the data for the write() operation.

DataTransfer:
Intent to Implement & Ship:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/NY8OPSzHGuE
WHATWG HTML spec bug: https://github.com/whatwg/html/issues/2190
Spec:
https://html.spec.whatwg.org/multipage/interaction.html#the-datatransfer-inte...
W3C WebPlatformTest PR: https://github.com/w3c/web-platform-tests/pull/5232

Async Clipboard:
W3C Spec: https://w3c.github.io/clipboard-apis/#async-clipboard-api

BUG=677564
==========

to

==========
Add constructor for DataTransfer

This is being added to support the Asynchronous Clipboard API, which
requires a DataTransfer object to store the data for the write() operation.

DataTransfer:
Intent to Implement & Ship:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/NY8OPSzHGuE
WHATWG HTML spec bug: https://github.com/whatwg/html/issues/2190
Spec:
https://html.spec.whatwg.org/multipage/interaction.html#the-datatransfer-inte...
W3C WebPlatformTest PR: https://github.com/w3c/web-platform-tests/pull/5232

Async Clipboard:
W3C Spec: https://w3c.github.io/clipboard-apis/#async-clipboard-api

BUG=677564

Review-Url: https://codereview.chromium.org/2784473003
Cr-Commit-Position: refs/heads/master@{#461281}
Committed:
https://chromium.googlesource.com/chromium/src/+/1f2f12faf6b42983525f917bd5fa...
==========

[commit-bot: I haz the power, 2017-04-01 00:10:38]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/1f2f12faf6b42983525f917bd5fa...