- From: Terence Eden <notifications@github.com>
- Date: Mon, 31 Jul 2017 09:26:03 +0000 (UTC)
- To: w3c/charter-html <charter-html@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 31 July 2017 09:26:29 UTC
For example - let me pick on the [Clipboard API use cases](https://www.w3.org/TR/clipboard-apis/#Cases). > There are many use cases for being able to change the default clipboard operations (cut/copy/paste). We have collected a few samples to demonstrate possible uses, although these may not all be supported by this specification. How can you write a specification without a clear understanding of *all* the possible use cases? You need to be able to say something like "As a web developer, I want to be able to directly read the clipboard of a user on my site, in order to..." Or, "As a visitor to a website, I want to know when a website tries to access my clipboard and grant or deny permission, so that I can be secure." Ideally, every use case should be backed up by research. Even if they're not, every part of the spec should clearly say how it addresses a use case. -- 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/charter-html/issues/146#issuecomment-319015420
Received on Monday, 31 July 2017 09:26:29 UTC