> websites can already trivially build editors that use copy and
> paste within the site itself
If that is true (I haven't done much work with web-based rich editors),
then I think that may have actually been Jonas's point: let's ensure that
same-origin clipboard operations are fully supported as they are in the
most modern browsers today. To ensure that remains true and/or is added in
browsers that may not currently support that notion 100%, we need to ensure
that the spec calls that out and also complies with or modifies other
related specs' contents. For example, the Editing spec may need to be
updated.
Sincerely,
James Greene
On Sun, Sep 14, 2014 at 7:54 AM, Dale Harvey <dale@arandomurl.com> wrote:
> websites can already trivially build editors that use copy and paste
> within the site itself, the entire problem is that leads to confusing
> behaviour when the user copies and pastes outside the website, which is a
> huge use case of the clipboard in the first place
>
> On 14 September 2014 08:57, Jonas Sicking <jonas@sicking.cc> wrote:
>
>> On Sat, Sep 13, 2014 at 1:58 PM, Hallvord R. M. Steen
>> <hsteen@mozilla.com> wrote:
>> > * paste: we allow reading clipboard contents if the paste event is not
>> synthetic and not triggered from a document.execCommand('paste') call.
>> There's also an exception that will allow scripts to read the clipboard
>> data in contexts where the UA is configured to allow this (could be for
>> example white-listed, trusted sites or apps).
>>
>> I think we should also allow reading data that was copied from the
>> same origin. That way a website can build an editor which has full
>> copy/paste capabilities as long as you are only editing within that
>> website.
>>
>> / Jonas
>>
>>
>
Received on Monday, 15 September 2014 16:35:27 UTC