Maybe execCommand('copy') isn't enabled outside editable region in some UAs?
- Ryosuke
On Tue, Sep 6, 2011 at 2:18 PM, Daniel Cheng wrote:
> 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,
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 wrote:
> On Mon, 05 Sep 2011 12:47:28 +0200, Hallvord R. M. Steen <
> hallv...@opera.com> wrote:
>
> On Mon, 05 Sep 2011 02
On Mon, 05 Sep 2011 12:47:28 +0200, Hallvord R. M. Steen
wrote:
On Mon, 05 Sep 2011 02:14:10 +0200, João Eiras
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 imple
On Mon, 05 Sep 2011 02:14:10 +0200, João Eiras
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, yo
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, or going even further, the
clipboard toolbar with buttons for the 3 actions (copy, cut