Should multiple webkitTransitionEnd events be called?

[joelambert]

The convention with real transitions is to fire a webkitTransitionEnd event for each property that is transitioned. Should Morf.js do the same? Currently it fires one event to say its finished.

https://github.com/joelambert/morf/blob/master/js/src/morf.js#L42

[jeremyckahn]

Good question. I think you could have both ways available - have your cake and eat it too. Perhaps you could have an API method that supports two function signatures, one that accepts a function that gets called once upon completion, and another that accepts an Object with functions mapped to property names. Here's a rough example of what I mean:

bindCompleteHandler(function () {
    console.log('Done!');
});

// Also works as:
bindCompleteHandler({
    'left': function () {
        console.log('Left done!');
    },
    'opacity': function () {
        console.log('Opacity done!');
    }
});

Not sure what the implications of this are regarding the overall flow of the code, just throwing an idea out there. I just wonder if restricting users to one approach or the other might cause problems down the line.