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

Re: Fwd: Re: CfC: new WD of Clipboard API and Events; deadline April 5

From: Ryosuke Niwa <rniwa@webkit.org>
Date: Tue, 6 Sep 2011 16:24:40 -0700
Message-ID: <CABNRm63KDFVo6n471=JT0b-rXAZyjXba-=TfgxxH0Wg-cRF+0w@mail.gmail.com>
To: "Hallvord R. M. Steen" <hallvord@opera.com>
Cc: Anne van Kesteren <annevk@opera.com>, Daniel Cheng <dcheng@chromium.org>, public-webapps <public-webapps@w3.org>
On Mon, Sep 5, 2011 at 3:52 AM, Hallvord R. M. Steen <hallvord@opera.com>wrote:

> On Mon, 05 Sep 2011 12:14:27 +0200, Anne van Kesteren <annevk@opera.com>
> wrote:
>
>  On Mon, 05 Sep 2011 12:13:35 +0200, Hallvord R. M. Steen <
>> hallvord@opera.com> wrote:
>>
>>> As in <LINK rel=prefetch> and <LINK rel=stylesheet>?
>>>
>>
>> Yes. But this would apply to <img> too of course; maybe they can become a
>> blob URL or some such?
>>
>
> Well, giving JS access to the clipboard's HTML will be next to useless if
> we remove just about everything :-p For the record, I think the spec as-is
> is too paranoid and that we probably should allow form elements (except
> input type=hidden).
>

So the problem we found is that certain productivity apps insert local file
paths, real user name, etc... into meta, link, etc... elements.  This is
problematic for users because users may not expect those information be
exposed to the Web when pasting some contents simply since they're not
visible.

I think the middle ground will be to let implementors decide exactly which
elements or attributes should be trimmed.

- Ryosuke
Received on Tuesday, 6 September 2011 23:25:50 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT