Getting an idea of what the expectation of behavior between on() and after() phase of a stopped event is.

gistfile1.js

var child       = new Y.EventTarget({ emitFacade: true }),
    parent      = new Y.EventTarget({ emitFacade: true }),
    grandparent = new Y.EventTarget({ emitFacade: true });
    
child.addTarget(parent);
parent.addTarget(grandparent);

child.publish('foo', {
    defaultFn: function () { console.log("default function"); }
});

child.on('foo', function (e) { console.log('child.on()'); });

parent.on('foo', function (e) {
    console.log('parent.on()');
    e.stopPropagation();
});

grandparent.on('foo', function (e) { console.log('grandparent.on()'); });

child.after('foo', function (e) { console.log('child.after()'); });
parent.after('foo', function (e) { console.log('parent.after()'); });
grandparent.after('foo', function (e) { console.log('grandparent.after()'); });

child.fire('foo');
// What do you think should be logged?

Okay, with the defaultFn, things don't change too much. Again, my expectation and my ideal behaviours differ:

I'd expect this to happen:

child.on()
parent.on()
default function
child.after()

But contrary to what others have said, I would want this to happen:

child.on()
default function
child.after()
parent.on()
parent.after()

To me it seems more logical that the after() of a child should precede the on() of a parent, and also it seems more convenient to fire the after() event even if propagation has stopped.