- From: <bugzilla@jessica.w3.org>
- Date: Thu, 23 Jan 2014 23:56:51 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23536 --- Comment #2 from Hallvord R. M. Steen <hsteen@mozilla.com> --- I think data: URLs have some drawbacks, memory usage is one. Imagine pasting a snippet of text from a Word document that has an embedded video.. The idea here is that once implementations have mangled the markup to add cid: URLs, the script can parse the markup (or, better yet, use event.clipboardData.documentFragment if we give the API a link to the parsed DOM..), rummage through the DOM to find cid: references, start file uploads for those clipboard parts and add placeholders to the pasted data that the script later can rewrite to reference the eventual server location(s) when file upload(s) finish. The cid: scheme avoids exposing any local paths or structures (which we're worrying about in https://bugzilla.mozilla.org/show_bug.cgi?id=665341 and similar bugs - thanks for making me aware of it BTW). (I'll have to ask implementors about this stuff though. They may well feel like it's too late to introduce this cid: concept - although AFAIK we don't really have any better concepts for those use cases yet..) -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 23 January 2014 23:56:52 UTC