- From: Daniel Cheng <dcheng@chromium.org>
- Date: Tue, 6 Sep 2011 14:18:15 -0700
- To: "public-webapps@w3.org" <public-webapps@w3.org>
- Message-ID: <CAF3XrKo6_AV5wkxJA9YAsvZmmCYx5DuZchF0LBapEfA8xqdDxA@mail.gmail.com>
Why do you need to create an element? Just call execCommand('copy') and setData('text/html', 'blah') in your copy handler. Daniel On Mon, Sep 5, 2011 at 03:57, João Eiras <joaoe@opera.com> wrote: > On Mon, 05 Sep 2011 12:47:28 +0200, Hallvord R. M. Steen < > hallvord@opera.com> wrote: > > On Mon, 05 Sep 2011 02:14:10 +0200, João Eiras <joao.eiras@gmail.com> >> wrote: >> >> Hi ! >>> >>> The spec for setData [1] states that this method when calling from a >>> cut/copy event sets new data on the clipboard. Unfortunately, this is >>> insufficient to implement the typical copy to clipboard button >>> >> >> It is indeed. However, you already have things like >> document.execCommand('copy') for that. >> >> > So lets say I have one of features which let me copy to the clipboard a > snippet of html to embed a video for instance, to paste somewhere. > > A script needs to create an element, put the contents inside, wrap a > selection around it, call execCommand('copy'), remove the element and shift > focus back to the button. > > Seems a bit overkill. Are you really sure it can't be made simpler ? The > feature is there already, theoretically. > >
Received on Tuesday, 6 September 2011 21:18:49 UTC