- From: <bugzilla@jessica.w3.org>
- Date: Wed, 18 Apr 2012 19:55:05 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16790 --- Comment #4 from Glenn Maynard <glenn@zewt.org> 2012-04-18 19:55:04 UTC --- Actually, I don't think microtasks is quite what auto-revoking URLs need. Instead, they should use stable states. Start an asynchronous task, await a stable state, and then revoke the URL. I think this is a better fit for that feature, because for example they happen between synchronously-executed <script>, where microtasks don't. That is, in <script>url = URL.createObjectURL(blob, {autoRevoke:true})</script><script>performXHR(url)</script> the XHR should fail, with the URL being revoked after the first script exits and before the second one starts. With microtasks, that may not happen. I could be wrong; I'm working from memory, and there are probably subtle side-effects of either approach which I'm missing. The discussion got sidetracked, so I don't know if anyone has fully reviewed this approach. http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/1316.html -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 18 April 2012 19:55:14 UTC