On Sep 1, 5:18 pm, "Nicolás Sanguinetti" <[EMAIL PROTECTED]> wrote:
> Anyway, the custom event solution seems tidy enough. What do the w3c
> specs say on xmlhttprequests and contentloaded, if anything?
They don't. Despite its name, the "DOMContentLoaded" event is not part
of any standard.
--~--
On 9/1/07, Thomas Fuchs <[EMAIL PROTECTED]> wrote:
>
> IMHO, "contentloaded" should be fired once, when the DOM of the
> initial page is completely loaded and parsed by the browser.
>
> ...
>
> I think making contentloaded too magic breaks POLS.
Actually it works the other way around for me. My m
IMHO, "contentloaded" should be fired once, when the DOM of the
initial page is completely loaded and parsed by the browser.
Loading in stuff via Ajax shouldn't trigger this event.
YMMV, but you can add a global ajax responder and fire a
"fragmentloaded" (or so) custom event, and oberve that
On Aug 31, 2007, at 12:34 AM, Andrew Dupont wrote:
> Jeff, my suggestion is to write your own Event.onReady function (or
> something like it) that wraps around the 1.6 event code.
Yeah, that's kind of what I figured. But since it's got to be a
pretty common situation, I thought it might deserv
Andrew Dupont wrote:
> ...
> Imagine you've got a page with some inline code that assigns stuff to
> DOMContentLoaded. Now imagine it's a fragment, not a full page, and
> you're loading it via Ajax.
>
> Jeff, my suggestion is to write your own Event.onReady function (or
> something like it) that w
On Aug 31, 2:12 am, "Mislav Marohnić" <[EMAIL PROTECTED]>
wrote:
> On 8/31/07, Jeff Watkins <[EMAIL PROTECTED]> wrote:
> Let me see if I'm getting this correctly. You are saying that you need to
> inject content in the DOM received by XHR ... while the current page is
> still being loaded? That
On 8/31/07, Jeff Watkins <[EMAIL PROTECTED]> wrote:
>
>
> For example, imagine you have a widget which would like to perform
> its initialisation only after the DOM is ready. It registers a
> listener for contentready on the document. All is fine. Now let's add
> Ajax to the mix. The widget is inst
Dan Webb's LowPro[1] "solves" this kind of issue by registering a
global Ajax.Responder that evaluates DOMContentReady behaviors
onComplete.
Thinking along similar lines, you could wrap Event.observe so that
observers set for contentloaded are also stored into a queue that gets
processed after e
