- From: Piotrek Koszuliński <notifications@github.com>
- Date: Fri, 14 Aug 2015 03:56:21 -0700
- To: w3c/editing <editing@noreply.github.com>
- Message-ID: <w3c/editing/issues/64/131075002@github.com>
> I am not sure what considerations went into that, but this is how I interpret this passage: > > > Scripts can not trigger paste actions, not even from user-initiated threads (though the spec leaves the door open to implementing specific permission UIs that will allow this on a per-site basis). > > http://www.whatcouldbewrong.com/articles/html5-clipboard-support/ Thanks for the link. You can ignore my previous comment because I incorrectly remembered that Chrome and FF will/do support user-initiated paste, while they only support paste and cut. Hallvord's post makes it super clear. I was wondering though, if the spec leaves the door open for user-initiated paste, what if I change browser's settings to allow clipboard access (if any implements this). Hypothetically, the `paste` command would work then in `contentEditable=true` but what would happen in `contentEditable=events`? AFAICS we don't need to spec it at all, because the `paste` event will be fired on the document, so it's the same case as with `copy`. It means that whatever happens `cE=events` should be safe (as @hallvors wrote). > Yeah, that true since if it doesn't do anything to the editing host by default. Agree. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/64#issuecomment-131075002
Received on Friday, 14 August 2015 10:56:51 UTC