Open HenryWales opened 1 year ago
Hello, can you give me more information? Does it happen during word testing or text reading, since you dropped both terms :smile:
It seems to be a JavaScript issue, I think there is a context issue somewhere (as we are working with two different frames).
I meant during text reading. This happens mostly when adding a new term as this takes more time to process.
The testing part referred to me trying out things to figure out why the issue was happening, until I could consistently reproduce it. I don't use LWT's built-in testing, as I find it inadequate.
It happened to me sometimes without understanding why.
After testing it looks related to the saving process in the frame with the definition. If clicking on another term that request to load an editing frame with definition before the saving process is finished, the saving will still work but the text body is not updated and the word keeps the color of its previous status. The term is still saved correctly and reloading the text corrects the glitch.