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
@stefanv, this was unfortunately introduced by your changes in #1036, and I didn't notice it initially (we really need an automated test suite for the JS code, badly).
Now, the alert dialog comes up for any closing of a page, even if it was already saved. Furthermore, the message which used to read
You have unsaved changes that will be lost if you leave this page.
now simply says true. I'm going to try to see if I can quickly fix it, but if I can't I'll just revert back the commit (with git revert) so we can fix things later. Now I'm worried that there may be other new bugs in the notebook introduced by this which we haven't seen yet.
Lesson learned: never merge again a 'cleanup' on javascript, since its semantics regarding this stuff are so finicky that a supposedly purely stylistic fix can break code.
The text was updated successfully, but these errors were encountered:
I've been looking through the code, and I can't quite understand what is causing this problem. Let me know if you can track it down, if not for now we'll need to revert. A bug is too high a price to pay to keep a syntax nanny happy :)
I just tried the latest version of the notebook (it seems the patch hasn't been reverted yet), and that works fine here as well (I did a reload to make sure I'm using the newest js).
@stefanv, this was unfortunately introduced by your changes in #1036, and I didn't notice it initially (we really need an automated test suite for the JS code, badly).
Now, the alert dialog comes up for any closing of a page, even if it was already saved. Furthermore, the message which used to read
now simply says
true
. I'm going to try to see if I can quickly fix it, but if I can't I'll just revert back the commit (withgit revert
) so we can fix things later. Now I'm worried that there may be other new bugs in the notebook introduced by this which we haven't seen yet.Lesson learned: never merge again a 'cleanup' on javascript, since its semantics regarding this stuff are so finicky that a supposedly purely stylistic fix can break code.
The text was updated successfully, but these errors were encountered: