Michał Gołębiowski-Owczarek

Your steps didn't work for me but after a few refreshes it suddenly kicked in. Very weird. In any case, the element stays in the DOM so it's Chrome that...

This thenable-uwrapping is required by the Promises/A+ spec; specifically [the promise resolution algorithm](https://promisesaplus.com/#the-promise-resolution-procedure). The relevant point is [2.3.3.3](https://promisesaplus.com/#point-56) which describes thenable unwrapping. In particular, [point 2.3.3.3.1](https://promisesaplus.com/#point-57) mandatest that the full...

I'm a little confused about this message, though: > jQuery.Deferred exception: opened.then is not a function If an object doesn't have a `then` method then it's not a thenable and...

Thanks for the report. Since the issue is already in 1.12, given limited team resources it's not likely to be fixed by the UI team; see the project status at...

A great analysis, thanks a lot! I'm surprised that using `performance.now()` gives worse results than using the timestamp since it's based on the same timer. I made a quick patch...

Re Firefox: the terrible graphs that I'm seeing are there only if I use the integrated graphics card in my MacBook. i.e. Intel Iris Pro 1536 MB. If I switch...

@dmethvin My quick patch made `jQuery.fx.tick` accept a timestamp parameter so that'd slightly change the API; to avoid that we'd need a wrapper function which might increase the code size...

Ah, you said it's as smooth as Chrome for you in Firefox on Windows 10. Do you mean it looks like the same graph as the second one from the...

> In here @mgol points out that timestamp dependant on graphics card (@dmethvin your card might just be in "good" category), is it not case? Possible. The current data points...

PR: #3151. Please review.