Rename Clipboard.idl to DataTransfer.idl to match the spec

Rename Clipboard.idl to DataTransfer.idl to match the spec

http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#the-datatransfer-interface

The spec uses DataTransfer and both Firefox and IE agrees.

BUG=348580
R=ch.dumez@samsung.com, tkent@chromium.org

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

[arv (Not doing code reviews), 2014-03-03 16:39:38]

2 questions.

1. I didn't rename the C++ files/classes. It can be done but I think people have
a better sense of what a Clipboard is than a DataTransfer.
2. Should we add a global alias for Clipboard with a deprecation warning. I
don't think we need to since this is not something that people useually touch
and it never worked outside Blink/WebKit.

Thanks for reviewing.

[sof, 2014-03-03 17:20:54]

On 2014/03/03 16:39:38, arv wrote:
> 2 questions.
> 
> 1. I didn't rename the C++ files/classes. It can be done but I think people
have
> a better sense of what a Clipboard is than a DataTransfer.
> 2. Should we add a global alias for Clipboard with a deprecation warning. I
> don't think we need to since this is not something that people useually touch
> and it never worked outside Blink/WebKit.
> 
> Thanks for reviewing.

2 - quite unlikely for some kind of detection logic to use it (and it only), as
you say. Try without?

The CL itself looks fine to me.

[Inactive, 2014-03-03 18:06:31]

lgtm but this needs API Owner approval.

On 2014/03/03 16:39:38, arv wrote:
> 2 questions.
> 
> 1. I didn't rename the C++ files/classes. It can be done but I think people
have
> a better sense of what a Clipboard is than a DataTransfer.

I agree with you, Clipboard is a bit clearer on implementation side.

> 2. Should we add a global alias for Clipboard with a deprecation warning. I
> don't think we need to since this is not something that people useually touch
> and it never worked outside Blink/WebKit.

I'll leave this up to tkent. I do think it is unlikely to break things but if we
want to be safe, having a deprecated Clipboard property on Window is definitely
a good solution.

[tkent, 2014-03-03 23:17:31]

lgtm.  This change looks safe.

[tkent, 2014-03-03 23:18:32]

I don't think we need to do 2.

[arv (Not doing code reviews), 2014-03-03 23:26:56]

The CQ bit was checked by arv@chromium.org

[commit-bot: I haz the power, 2014-03-03 23:27:13]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/arv@chromium.org/183743013/20001

[commit-bot: I haz the power, 2014-03-04 12:55:51]

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

[commit-bot: I haz the power, 2014-03-04 12:55:51]

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

[arv (Not doing code reviews), 2014-03-04 15:51:16]

The CQ bit was checked by arv@chromium.org

[commit-bot: I haz the power, 2014-03-04 15:51:37]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/arv@chromium.org/183743013/20001

[arv (Not doing code reviews), 2014-03-04 23:22:01]

Committed patchset #1 manually as r6c112cc (presubmit successful).

[arv (Not doing code reviews), 2014-03-05 15:47:02]

On 2014/03/04 23:22:01, arv wrote:
> Committed patchset #1 manually as r6c112cc (presubmit successful).

This was not committed... as you can see that is not a valid revision...
relanding

[arv (Not doing code reviews), 2014-03-05 16:02:01]

Committed patchset #1 manually as r168494 (presubmit successful).