W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

Re: [clipboard] Semi-Trusted Events Alternative

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 15 Sep 2014 14:32:57 -0700
Message-ID: <CA+c2ei8GkjLB3Z46FTYxDh6y5=URYih85Gzj7-iZvWz5urhKrw@mail.gmail.com>
To: "Hallvord R. M. Steen" <hsteen@mozilla.com>
Cc: Ben Peters <Ben.Peters@microsoft.com>, "James M. Greene" <james.m.greene@gmail.com>, Perry Smith <pedzsan@gmail.com>, Webapps WG <public-webapps@w3.org>
On Mon, Sep 15, 2014 at 1:42 PM, Hallvord R. M. Steen
<hsteen@mozilla.com> wrote:
>> 2. Allow reading data from the clipboard at any time if the data there
>> originated from the current origin. Thereby making the API as helpful
>> as possible for the case when data is copied within a website.
> So, I'm not yet "sold" on this suggestion. As I said already it's interesting - but it adds complexity to security/privacy-sensitive programming logic, and it might add layers of confusion for users. "The paste button worked fine a moment ago, why doesn't it work now??". "Copying from tab A worked fine and I could paste, copying from tab B fails??".

If we enable the website to check if it has the ability to read data
from the clipboard, then the website can gray out the "paste" button
as appropriate. Or replace it with text indicating that the user has
to use other actions to paste.

But yes, it does create a more complex UI for the user. And a more
complex API for the author.

/ Jonas
Received on Monday, 15 September 2014 21:33:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:26 UTC