Re: DOM-Events: Non-bubbleable means non-capturable?

Sergey Ilinsky wrote:
> but the test case given below proves different behaviour in FF.

For text inputs, Firefox has a capturing listener that calls stopPropagation() 
and fires before any capturing listeners on the page (conceptually, it's a 
listener on the "parent of the window" or so).  Hence no event in your case.

Also, in release versions of Firefox some events (eg. image load events) do not 
capture when they should.  This is fixed in development builds.

I suggest either testing the focus event on an anchor instead of a text input or 
testing some non-focus and non-blur event.

-Boris