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
We have forced to skip the MutationObserver implementation, which in turns causes to fallback to the MessageChannel implementation, and we see that it works correctly.
Seems to be another faulty MutationObserver webkit impl.
Is there a way to force to skip the MutationObserver implementation without forking core-js?
The text was updated successfully, but these errors were encountered:
lucalooz
added a commit
to lucalooz/core-js
that referenced
this issue
Dec 28, 2020
We're getting some strange issues, only in some conditions, where the microtask implementation doesn't work correctly with
flush
that's not executed.Similar to:
We have forced to skip the
MutationObserver
implementation, which in turns causes to fallback to theMessageChannel
implementation, and we see that it works correctly.Seems to be another faulty
MutationObserver
webkit impl.Is there a way to force to skip the
MutationObserver
implementation without forking core-js?The text was updated successfully, but these errors were encountered: