Not sure that there's a more deterministic approach - if so, it's
beyond my limited Javascript knowledge.
Specifically what are you trying to accomplish by wiring an event
handler to fire after the default action?
On Aug 20, 10:39 pm, Tom Worster <f...@thefsb.org> wrote:
> thanks.
>
> i thought of using a timeout and it could probably be made to work fairly
> well. but i'd be left with the worry that some user's crummy old browser and
> computer that's too busy doing other things might need a longer delay than i
> set.
>
> we can insert event handlers at the beginning of the event propagation
> chain. or catch the event later as it bubbles. but i've never heard of
> attaching a handler to the chain after the browser has done its bit. i was
> wondering if this was just my ignorance or if it just can't be done that
> way.
>
> On 8/20/09 8:45 PM, "ak732" <ask...@gmail.com> wrote:
>
>
>
> > This is crude, but might work for you...
>
> > $("#someId").click()(function() {
> > set_timeout(function() {
> > // stuff to be done 2ms from now
> > }, 2);
> > });
>
> > You might have to play with the set_timeout delay a bit, 2ms might be
> > too short.
>
> > On Aug 20, 3:47 pm, Tom Worster <f...@thefsb.org> wrote:
> >> is there a way to set up a page so that a event handler function is bound
> >> to
> >> a DOM object and event but it runs _after_ the browser's default action is
> >> complete?
