- From: <bugzilla@jessica.w3.org>
- Date: Fri, 13 Jul 2012 19:29:54 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17765 --- Comment #6 from Glenn Maynard <glenn@zewt.org> 2012-07-13 19:29:54 UTC --- (In reply to comment #5) > I believe parsing always happens synchronously because it can fail. > > The only way I can see this work is by tying some kind of flag to the > identifier that is set after the task in which the associated blob URL is being > parsed and anytime after that when the same blob URL is being parsed the result > ends up being about:invalid or some such (about:invalid is a URL representing a > network error). Because if it would still be the same URL there would be no way > to distinguish it when you start fetching the thing. (The blob data would be > stored after parsing along with the identifier.) Sorry, I'm having trouble parsing this. You can parse/resolve/fetch the same autoRevoke blob URL any number of times, so why would it resolve to about:invalid? -- 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 Friday, 13 July 2012 19:29:55 UTC