Combining DOM0 and DOM2 event handlers - cancelling of event possible in the DOM0 handler?

Please consider the following problem:

(1) You have assigned an inline event handler to a DOM element, like so <a id="link1" href="..." onclick=" ... ´">

(2) You also assign one or more further event handler(s) to the onclick event of link1 with the DOM2 or IE-specific assignment mechanism.

The verified behavior in Firefox 3.019 and IE7 is: the handler assigned in (1) is executed BEFORE all handlers assigned in (2) in case of a click. This is nice (so, probably, nothing written into stone ...). But let's rely on this behaviour for a moment.

QUESTION now: is it possible to CANCEL the bubbling of the click event to the handlers assigned in (2) WITHIN the handler assigned in (1)?

Before you scream: Sure, why not, see the following: Assume you assign onclick="if (ready1) return true; else return loading(event);" to link1 and define loading to be

function loading(e) {
    // alert("Still loading functionality - sorry, slow line perhaps...");
    // no propagation
    if( e.stopPropagation ) { e.stopPropagation(); }
    e.cancelBubble = true;
    return false; // Cancel default handling
}

in some script tag above. This DOES NOT prevent propagation (neither in FF3.019 nor IE) to the handlers assigned in (2).

Any开发者_StackOverflow社区 hint appreciated!

Context (or: why would I want to do this?):

A) Lazy / Late loading of Javascript for fast rendering of content.

-> you want to inform the user that some functionality is still loading (instead of simply disabling an UI element, which is not really user-friendly -- why is this button disabled?). You also want to use minimal Javascript already embedded into the page, because loading a Javascript library first with an additional request somewhat defeats the purpose (otherwise you could, of course, use one of the implemented mechanisms that allow event registration with guaranteed execution sequence (which you'll need for B, see below)

and B) you also want to "set the beasts free" at a single "atomic" point in time, that is: you don't want to be forced to integrate/change all handlers assigned in (2) to wait for some kind of signal "now you are allowed to work because everything is loaded", you simply want to give this signal to the head of the event processing chain (the handler assigned in (1)) only, which then can simply start propagating the event to whatever may come (otherwise, partial reactions to user input may occur, because some functionality is already attached and other functionality not -- which is potentially worse than doing nothing ;)

Short answer: No.

Long answer: You can use the first handler to set a variable that the 2nd (and subsequent) handlers check. Here's a quick example

<div id="outer">
  <a id="link1" href="#" onclick="return loading();">test</a>
</div>

<script type="text/javascript" src="http://jqueryjs.googlecode.com/files/jquery-1.3.2.min.js"></script>
<script type="text/javascript">

var passCheck = false;

setTimeout( function()
{
  passCheck = true;
}, 5000 );

function loading()
{
  alert( 'a#link1 was clicked!' );
  return false;
}

$(function()
{
  $('#link1').click( function( event )
  {
    if ( !passCheck )
    {
      event.stopPropagation();
    }
  });

  $('#outer').click( function( event )
  {
    alert( 'div#outer was clicked!' );
  });
});

</script>

This all feels very hacky though. It feels like you should use some completion callbacks instead, or the application of some continuation passing style.