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
If the browser requests a lump of JS at the marked point in the code, the generated JS can look like "wipe out everything in the document body; then get the button element and..."; but the button element no longer exists, so executing the JS raises an error in the browser, which ends up closing the browser window. (This won't always happen, because the order of the JS commands is nondeterministic.)
I think DocumentChangeTracker needs a serious refactor. It's always felt a little wonky to me, and the fact that this kind of error is possible (even though I tried to threadsafe it) suggests something is horribly wrong with the architecture.
The text was updated successfully, but these errors were encountered:
Consider this code:
If the browser requests a lump of JS at the marked point in the code, the generated JS can look like "wipe out everything in the document body; then get the button element and..."; but the button element no longer exists, so executing the JS raises an error in the browser, which ends up closing the browser window. (This won't always happen, because the order of the JS commands is nondeterministic.)
I think
DocumentChangeTracker
needs a serious refactor. It's always felt a little wonky to me, and the fact that this kind of error is possible (even though I tried to threadsafe it) suggests something is horribly wrong with the architecture.The text was updated successfully, but these errors were encountered: