Re: File API "oneTimeOnly" is too poorly defined

On Thu, Mar 29, 2012 at 12:36 PM, Glenn Maynard <glenn@zewt.org> wrote:

> oneTimeOnly (a poor name in this proposal) would simply queue a microtask
> to revoke the URL.
>
> This is simpler, and answers a lot of questions.  It means you can use the
> URL as many times as you want synchronously, since it's not released until
> the script returns.  Any cases where the ordering may not be strictly
> defined (eg. the <video><video> case in
> http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/1265.htmlmay be like this; I don't know how innerHTML works, exactly) are now
> defined: both <video> elements would get the object.
>

That sounds like a pretty good idea.

It might be a bit better to revoke the URL at the next stable state.
Microtask checkpoints can happen during synchronous script execution.

Rob
-- 
“You have heard that it was said, ‘Love your neighbor and hate your enemy.’
But I tell you, love your enemies and pray for those who persecute you,
that you may be children of your Father in heaven. ... If you love those
who love you, what reward will you get? Are not even the tax collectors
doing that? And if you greet only your own people, what are you doing more
than others?" [Matthew 5:43-47]