Re: [whatwg] DOMContentLoaded, load and current document readiness

2012-08-30 Thread Ian Hickson
On Thu, 30 Aug 2012, Jonas Sicking wrote: > > > > That's what the spec says, no? > > I thought so, but the comments in this thread made me think otherwise. > If that's the case then I'm happy. I strongly recommend only believing what the spec says, not what is said in threads. :-) -- Ian Hick

Re: [whatwg] DOMContentLoaded, load and current document readiness

2012-08-30 Thread Jonas Sicking
On Thu, Aug 30, 2012 at 11:30 AM, Ian Hickson wrote: > On Thu, 30 Aug 2012, Jonas Sicking wrote: >> On Wed, Aug 29, 2012 at 8:34 PM, Ian Hickson wrote: >> > On Sun, 17 Jun 2012, Jonas Sicking wrote: >> >> > On Wed, 25 Apr 2012, Jonas Sicking wrote: >> >> >> >> >> >> Hmm.. how long as that been th

Re: [whatwg] DOMContentLoaded, load and current document readiness

2012-08-30 Thread Ian Hickson
On Thu, 30 Aug 2012, Jonas Sicking wrote: > On Wed, Aug 29, 2012 at 8:34 PM, Ian Hickson wrote: > > On Sun, 17 Jun 2012, Jonas Sicking wrote: > >> > On Wed, 25 Apr 2012, Jonas Sicking wrote: > >> >> > >> >> Hmm.. how long as that been the case? I thought that when we > >> >> originally implemented

Re: [whatwg] DOMContentLoaded, load and current document readiness

2012-08-29 Thread Jonas Sicking
On Wed, Aug 29, 2012 at 8:34 PM, Ian Hickson wrote: > On Sun, 17 Jun 2012, Jonas Sicking wrote: >> > On Wed, 25 Apr 2012, Jonas Sicking wrote: >> >> >> >> Hmm.. how long as that been the case? I thought that when we >> >> originally implemented @defer we ran them before DOMContentLoaded was >> >>

Re: [whatwg] DOMContentLoaded, load and current document readiness

2012-08-29 Thread Ian Hickson
On Sun, 17 Jun 2012, Jonas Sicking wrote: > > On Wed, 25 Apr 2012, Jonas Sicking wrote: > >> > >> Hmm.. how long as that been the case? I thought that when we > >> originally implemented @defer we ran them before DOMContentLoaded was > >> fired for various internal sanity reasons as well as becau

Re: [whatwg] DOMContentLoaded, load and current document readiness

2012-06-16 Thread Jonas Sicking
On Wed, Jun 13, 2012 at 11:21 PM, Ian Hickson wrote: > On Fri, 20 Apr 2012, Henri Sivonen wrote: >> On Tue, Jan 10, 2012 at 2:10 AM, Ian Hickson wrote: >> > On Tue, 31 May 2011, Henri Sivonen wrote: >> >> >> >> Recently, there was discussion about changing media element state in >> >> the same ta

Re: [whatwg] DOMContentLoaded, load and current document readiness

2012-06-13 Thread Ian Hickson
On Fri, 20 Apr 2012, Henri Sivonen wrote: > On Tue, Jan 10, 2012 at 2:10 AM, Ian Hickson wrote: > > On Tue, 31 May 2011, Henri Sivonen wrote: > >> > >> Recently, there was discussion about changing media element state in > >> the same task that fires the event about the state change so that > >>

Re: [whatwg] DOMContentLoaded, load and current document readiness

2012-04-25 Thread Jonas Sicking
On Fri, Apr 20, 2012 at 3:43 AM, Henri Sivonen wrote: > On Tue, Jan 10, 2012 at 2:10 AM, Ian Hickson wrote: >> On Tue, 31 May 2011, Henri Sivonen wrote: >>> >>> Recently, there was discussion about changing media element state in the >>> same task that fires the event about the state change so th

Re: [whatwg] DOMContentLoaded, load and current document readiness

2012-04-20 Thread Henri Sivonen
On Tue, Jan 10, 2012 at 2:10 AM, Ian Hickson wrote: > On Tue, 31 May 2011, Henri Sivonen wrote: >> >> Recently, there was discussion about changing media element state in the >> same task that fires the event about the state change so that scripts >> that probe the state can make non-racy conclusi

Re: [whatwg] DOMContentLoaded, load and current document readiness

2012-01-09 Thread Ian Hickson
On Tue, 31 May 2011, Henri Sivonen wrote: > > Recently, there was discussion about changing media element state in the > same task that fires the event about the state change so that scripts > that probe the state can make non-racy conclusions about whether a > certain event has fired already. >

Re: [whatwg] DOMContentLoaded, load and current document readiness

2011-05-31 Thread Boris Zbarsky
On 5/31/11 6:37 PM, Aryeh Gregor wrote: How about: [ugly code snipped] That does work, yes (assuming your readyState check is correct; if not it can be fixed to be correct). As you note, expecting web authors to do this is silly. Forget figuring out or not; we just don't want to inflict t

Re: [whatwg] DOMContentLoaded, load and current document readiness

2011-05-31 Thread Aryeh Gregor
On Tue, May 31, 2011 at 5:02 AM, Henri Sivonen wrote: > Currently, there seems to be no correct non-racy way to write code that > probes a document to determine if DOMContentLoaded or load has fired and > runs code immediately if the event of interest has fired or adds a > listener to wait for the

Re: [whatwg] DOMContentLoaded, load and current document readiness

2011-05-31 Thread Jonas Sicking
On Tue, May 31, 2011 at 2:02 AM, Henri Sivonen wrote: > Recently, there was discussion about changing media element state in the > same task that fires the event about the state change so that scripts > that probe the state can make non-racy conclusions about whether a > certain event has fired al

[whatwg] DOMContentLoaded, load and current document readiness

2011-05-31 Thread Henri Sivonen
Recently, there was discussion about changing media element state in the same task that fires the event about the state change so that scripts that probe the state can make non-racy conclusions about whether a certain event has fired already. Currently, there seems to be no correct non-racy way to