Closed ljharb closed 9 years ago
I think in this early implementation stage we should just override the promise implementation. We are already doing that on chrome I think. Note that we do already use the native Promise scheduler if available, though.
Will we continue to use the native Promise scheduler on Safari 7.1 with this change?
I believe so. Look for makePromiseAsap
in the code.
--scott
( http://cscott.net/ )
@cscott, what do you think? Would it be worth just wrapping Safari 7.1's native Promises rather than completely overriding them?
Fixes #288.