54744dd3a9
Fortunately, this was just a visual bug, and the current note was always saved correctly.
The reproduction steps were:
1. Open two notes, A and B.
2. Modify note A, and then switch to note B. This causes note A to save.
3. The save happens to take a long time (which you can force with a sleep).
4. While the save is executing, quickly modifiy note B.
5. When the original save completes, the "save" button changes to "saved",
even though note B has been modified and is not saved.
The solution was simply to check whether the focused note is dirty before changing to a "saved" button.
|
||
|---|---|---|
| .. | ||
| Editor.js | ||
| Invoker.js | ||
| MochiKit.js | ||
| MochiKit_LICENSE | ||
| Wiki.js | ||