Created by: Harris-Miller
this is very similar to pull request #13286 what @tdolsen did there is change .emulateTransitionEnd to take either a number or a string. if you pass in a number, it acts the same as before. if you pass in a string (presumably one from $el.css('transition-duration'), thus giving you "2s" or "2s, 3s", etc) it will parse those, determine which is the greatest, and return that value in milliseconds
now that's a great start to fixing .emulateTransionEnd, however it leaves out 2 key factors
- it does not take into account if transition-delay is not zero
- you have to keep track of your css transition times in your javascript
i figured that because in practice you would always be calling .emulateTransitionEnd on an element with a transition, we can just fetch the duration and delays times right from the element using $.fn.css
this way we no longer have to pass what the supposed transition time to .emulateTransitionEnd, so when we make changes to those transition in css, we don't have to worry about making changes to our js as well
and second, obviously, i'm taking into account both duration and delay
i'm made changes to transition.js, implementing what i explained about, and also removed the arguments for all location that .emulateTransitionEnd is calls