- From: Tim Berners-Lee <timbl@w3.org>
- Date: Thu, 10 Jun 2010 19:31:13 +0200
- To: David Booth <david@dbooth.org>
- Cc: "L. David Baron" <dbaron@dbaron.org>, "Roy T. Fielding" <fielding@gbiv.com>, ashok.malhotra@oracle.com, Noah Mendelsohn <nrm@arcanedomain.com>, "www-tag@w3.org" <www-tag@w3.org>
On 2010-06 -10, at 02:35, David Booth wrote: > On Fri, 2010-06-04 at 19:27 -0700, L. David Baron wrote: > [ . . . ] >> The ability to manipulate what a user is copying is also important >> for applications on the Web. If you're using a Web app like Google >> Docs, you want copy to copy a useful representation, not the >> internal representation that the editor uses. > > But it is the *browser* that renders things like HTML, plain text, PDF, > etc. -- not javascript. Why should javascript be given the ability to > mess with it *after* the user has selected and told the browser to > *copy* it? Well, for example, the Tabulator would want to figure out which bit of HTML rendering you had deselected and return as a clipboard option the underlying RDF model data. Tim
Received on Thursday, 10 June 2010 17:31:26 UTC