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
[Violation] 'readystatechange' handler took 678ms
RemoteFiler.js:21 [Violation] 'message' handler took 193ms
[Violation] Forced reflow while executing JavaScript took 78ms
RemoteFiler.js:21 [Violation] 'message' handler took 274ms
[Violation] Forced reflow while executing JavaScript took 70ms
compatibility.js:35 [Violation] 'load' handler took 208ms
[Violation] Forced reflow while executing JavaScript took 89ms
[Violation] Forced reflow while executing JavaScript took 41ms
[Violation] Forced reflow while executing JavaScript took 35ms
[Violation] Forced reflow while executing JavaScript took 33ms
[Violation] Forced reflow while executing JavaScript took 39ms
Noticing this for the first time tonight in Chrome. It's related to us using MessageChannel to send things over to the iframe and back, and I guess blocking on it returning? We should see if we can deal with any of it.
The text was updated successfully, but these errors were encountered:
@edyedy123 this is not going to be an easy bug to fix, FYI. You are welcome to try it, but I really have no idea how to get you started on it. If you still want this, let me know; but you might also have an easier time with something else. Let me know.
Noticing this for the first time tonight in Chrome. It's related to us using
MessageChannel
to send things over to the iframe and back, and I guess blocking on it returning? We should see if we can deal with any of it.The text was updated successfully, but these errors were encountered: