I'm glad to see you guys taking time to put context sensitivity into these
methods. If you do this right, the framework should support being loaded and
consumed within an arbitrary context... that is important to me at least...
so thanks for trying so hard.

On 9/6/07, Mislav Marohnić <[EMAIL PROTECTED]> wrote:
> on 9/7/07, jdalton <[EMAIL PROTECTED]> wrote:
> >
> >
> > However, on a separate note, I am concerned about the real
> > window.onload event triggering while in the middle of executing the
> > observers for the emulated "contentLoaded".
> > So far though, I have gotten 0% feedback from the Core team about this
> > concern.
> This is the current implementation for the wrapper that fires
> "contentloaded" event:
>   function fireContentLoadedEvent() {
>     if (fired) return;
>     if (timer) window.clearInterval(timer);
>     document.fire("contentloaded");
>     fired = true;
>   }
> If we move "fired = true" above " document.fire()", will it be OK then?
> Then there is really no chance of fireContentLoadedEvent() to be called
> simultaneously.
> >

Ryan Gahl
Manager, Senior Software Engineer
Nth Penguin, LLC
WebWidgetry.com / MashupStudio.com
Future Home of the World's First Complete Web Platform
Inquire: 1-262-951-6727
Blog: http://www.someElement.com

You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 

Reply via email to