Notes not updating until the page is refreshed

Posted under Bugs & Features

NWSiaCB

For the past couple days, I've noticed this problem...

Note boxes are red when created or there are unsaved changes such as to size, then black when saved. For the past couple days, they stay red until I refresh the page. That, by itself, isn't so bad, but if I edit the box again, it creates a duplicate box because, apparently, the webpage thinks there wasn't a box already there to edit, so it creates a new one.

I wondered if this was just me, some odd Firefox script bug, but I've seen this in translations done by others, as well.

The result is overlapping slightly different text boxes if someone makes a note, then tries to edit it. (Creating increasing note opacity.) The first box, the one that the user tried to edit because it was presumably wrong, is also the one that "wins ties" and sits on top, as well.

Reply
NNescio

NWSiaCB said:

For the past couple days, I've noticed this problem...

Note boxes are red when created or there are unsaved changes such as to size, then black when saved. For the past couple days, they stay red until I refresh the page. That, by itself, isn't so bad, but if I edit the box again, it creates a duplicate box because, apparently, the webpage thinks there wasn't a box already there to edit, so it creates a new one.

I wondered if this was just me, some odd Firefox script bug, but I've seen this in translations done by others, as well.

The result is overlapping slightly different text boxes if someone makes a note, then tries to edit it. (Creating increasing note opacity.) The first box, the one that the user tried to edit because it was presumably wrong, is also the one that "wins ties" and sits on top, as well.

Ｉ　faced the exact same issue too. Notes remain red when you create them, and trying to edit them in this state will generate additional notes instead of applying the edit properly. Refreshing the post before editing seems bypass this issue somewhat, but this is quite annoying to do.

OMGkillitwithfire reported facing similar problems in a comment on post #2528594. BrokenEagle as well in post #2527315, and he also opened a ticket on github. See issue #2747.

Reply
1