On 3/15/14 11:36 AM, Kyle Simpson wrote:
The `async=false` stuff in the spec talks about dynamically loaded (not parser
loaded) scripts going into a queue so they are downloaded in parallel, but
executed in request-order from the queue.
Then those are guaranteed to be serialized.
The questi
On 15 March 2014 15:51, Kyle Simpson wrote:
> But there was … suggestions about markup-only mechanisms for handling …
> the use-cases in a way that … eliminate any need for script loaders.
>
Yep, markup is important for preparsers. /
>> I'd say the first syntax is a bit verbose for what I was dreaming 4 years
>> ago when I started asking for a simple script preloading mechanism, but
>> it's just this side of acceptable. If we have to take the second approach,
>> I say that's unacceptably more verbose/complex and falls short of
>> As I noted above, what we need to know (and I guess we need to know this
>> from all browsers) if there's a *guarantee* of a->b->c execution order (even
>> if all 3 are executing async)
>
> I don't believe there is such a guarantee, unless the spec spells it out
> explicitly.
The `async=fa
On 15 March 2014 00:35, Kyle Simpson wrote:
> there's a seemingly implicit requirement that we have to get both ES6
> promises and DOM promises to land for these suggested approaches to work.
ES6 promises are already in Chrome stable, they're on the route to stable
in Firefox. Promises will onl
On 15 March 2014 00:31, Kyle Simpson wrote:
>
> I'd say the first syntax is a bit verbose for what I was dreaming 4 years
> ago when I started asking for a simple script preloading mechanism, but
> it's just this side of acceptable. If we have to take the second approach,
> I say that's unacceptab
Thanks, updated my code examples to reflect this
On 14 March 2014 23:57, Boris Zbarsky wrote:
> On 3/14/14 6:04 PM, Jake Archibald wrote:
>
>> Any guarantees of ordering if fully cached?
>>
>
> I believe no.
>
> -Boris
>
On 3/14/14 8:31 PM, Kyle Simpson wrote:
As I noted above, what we need to know (and I guess we need to know this from all
browsers) if there's a *guarantee* of a->b->c execution order (even if all 3
are executing async)
I don't believe there is such a guarantee, unless the spec spells it out
There is no such thing as "DOM promises".
From: Kyle Simpson<mailto:get...@gmail.com>
Sent: 3/14/2014 20:35
To: whatwg@lists.whatwg.org<mailto:whatwg@lists.whatwg.org>
Subject: Re: [whatwg] Promise-vending loaded() & ready() methods
I'd also like to make the observation that putting .loaded()
together with
>> So, if that's how we think this would work, we need to understand how the
>> `execScript(..)` logic is going to be treated. Is creating a
On 3/14/14 6:04 PM, Jake Archibald wrote:
Any guarantees of ordering if fully cached?
I believe no.
-Boris
On 14 March 2014 21:05, Boris Zbarsky wrote:
> On 3/14/14 5:03 PM, Jake Archibald wrote:
>
>> Do you know what browsers do with a fully cached script?
>>
>
> "
On 3/14/14 5:03 PM, Jake Archibald wrote:
Do you know what browsers do with a fully cached script?
"" is always executed async when inserted into the DOM,
cached or not.
"