- From: Johannes Wilm <notifications@github.com>
- Date: Fri, 19 Aug 2016 08:46:01 -0700
- To: w3c/editing <editing@noreply.github.com>
- Message-ID: <w3c/editing/issues/144/241054998@github.com>
> Have you seen the [async clipboard api proposal](https://discourse.wicg.io/t/proposal-modern-asynchronous-clipboard-api/1513)? I believe it addresses your concerns (but with support for proper permissions rather than assuming that "a user initiated action" is the same as "user grants full permission to access clipboard"). @garykac I had none seen that proposal and it is exactly what I was asking for! The part I proposed about not changing the security model was just so that the discussion about creating such a method being unsafe could be minimized (this had been mentioned when this came up previously). I will leave all further commentary on that on the WICG page. This takes care of one issue with the clipboard. If we now agree on going with https://github.com/w3c/editing/issues/144#issuecomment-240558462 then there is still one remaining issue with the clipboard: How can the user prevent copying to the clipboard from happening altogether without intercepting keydown/up/press events? @garykac Do you think this is something you guys eventually could figure out to do within the clipboard api? Unless anyone here disagrees with it, I would suggest I start updating the input-events draft accordingly once the FPWD proposal is through, which should be August 22. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/144#issuecomment-241054998
Received on Friday, 19 August 2016 15:46:29 UTC