You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just tried to use the polyfill in Chrome (latest) and it is replacing the default implementation instead of properly detecting it.
The problem seems to be in this code fragment:
if (P && Object.prototype.toString.call(P.resolve()) === '[object Promise]' && !P.cast) {
return;
}
Object.prototype.toString.call(P.resolve()) is returning '[object Object]'. Can anyone else reproduce this behavior? The fix should be simple, buit I'd like to know why this approach is being used to detect the default Promise.
The text was updated successfully, but these errors were encountered:
Object.prototype.toString.call(P.resolve()) is returning '[object Object]'. Can anyone else reproduce this behavior? The fix should be simple, buit I'd like to know why this approach is being used to detect the default Promise.
this version of chrome still has a bugy promise implementation, so we choose our implementation which does not suffer those same issues.
Hi,
I just tried to use the polyfill in Chrome (latest) and it is replacing the default implementation instead of properly detecting it.
The problem seems to be in this code fragment:
if (P && Object.prototype.toString.call(P.resolve()) === '[object Promise]' && !P.cast) {
return;
}
Object.prototype.toString.call(P.resolve()) is returning '[object Object]'. Can anyone else reproduce this behavior? The fix should be simple, buit I'd like to know why this approach is being used to detect the default Promise.
The text was updated successfully, but these errors were encountered: