- From: <bugzilla@jessica.w3.org>
- Date: Mon, 14 Oct 2013 15:05:17 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23431 --- Comment #2 from Arun <arun@mozilla.com> --- One "pro" of moving everything to Fetch would be to have a central place to accommodate all the (proliferating) schemes. For instance, File API defines request-response behavior for the blob: scheme, much of which is reproduced in mediastream: URLs. Then, the FileSystem API will define the filesystem: scheme, which is currently implemented in Chrome, and which the specification will standardize. If all of it is routed via Fetch, we'll have a single normative source for URL dereferencing. But I'm not *strongly* opinionated on this, and don't mind the solution of it living in separate specifications. For "LC" purposes, the File API will define blob: and maybe successor drafts (including Fetch) can deal with the protocol as it evolves (hopefully not too much). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 14 October 2013 15:05:19 UTC