On Tue, 17 May 2011 15:50:30 +0900, Paul Libbrecht p...@hoplahup.net
wrote:
you seem to have not included João Eiras' answer:
Seems I overlooked that indeed. I thought something similar but didn't
include this, so it's good that João brought it up.
Le 5 mai 2011 à 04:34, João Eiras a
On Wed, May 18, 2011 at 8:10 PM, Hallvord R. M. Steen
hallv...@opera.com wrote:
Practically, the other downside is that since we re-use HTML5's DataTransfer
for clipboardData, this will have to be defined in the HTML spec - since
it's a new feature I guess that at this point means it will go
Hallvord,
you seem to have not included João Eiras' answer:
Le 5 mai 2011 à 04:34, João Eiras a écrit :
A synchronous XHR solves this use case and there are no magic locks.
Although I haven't explicitly tried to implement it and clearly feel it a
synchronous XHR can block the UI in an ugly
On Wed, 04 May 2011 02:26:22 +0900, Paul Libbrecht p...@hoplahup.net
wrote:
In many of the scenarios I have working for, the content to be put on
the clipboard would come from a luxury knowledge structure on the
server, one that has access to some semantic source and can infer
useful
On , Paul Libbrecht p...@hoplahup.net wrote:
Hello list,
As noted in the thread about security started by Halvord:
In many of the scenarios I have working for, the content to be put on the clipboard would
come from a luxury knowledge structure on the server, one that has access to
some
Hello list,
As noted in the thread about security started by Halvord:
In many of the scenarios I have working for, the content to be put on the
clipboard would come from a luxury knowledge structure on the server, one
that has access to some semantic source and can infer useful
On Tue, May 3, 2011 at 10:26 AM, Paul Libbrecht p...@hoplahup.net wrote:
As noted in the thread about security started by Halvord:
In many of the scenarios I have working for, the content to be put on the
clipboard would come from a luxury knowledge structure on the server, one
that has
Ryosuke,
Le 3 mai 2011 à 21:15, Ryosuke Niwa a écrit :
Would it be thinkable to *lock* the copy event until either a timeout occurs
or an unlock is called?
No. We definitely don't want to lock a local system resource for some random
web service that may potentially fail to release the
