https://bugs.documentfoundation.org/show_bug.cgi?id=124603
--- Comment #15 from László Németh <[email protected]> --- (In reply to Gabriel Masei from comment #12) > Thanks Laszlo for your fix! I've tested it by building the master branch and > running locally and it works. > > However, I think that the solution is incomplete. The state of the word is > changed only if the user presses the up or down keys. This is good but not > enough. The issue still manifests if the user performs any other actions > (like left/right keys or mouse to change the cursor position or perform a > different action, Ctrl + S to save the document, mouse to navigate through > menu for choosing an option, ...). I think that the update of the word state > should be done after any other action beside editing the word. Maybe we > should update the state at "leave the current word" event, if this event is > available. Or to update the word after any action from the user. I don't > know if the last suggestion is feasible as it could slow the editing but, on > the other hand, this will include all cases. @Gabriel: you are right, this solves only the most annoying part of the problem: replacing the mandatory editing with a more comfortable solution. The other part of the problem was filed in Bug 136294. (Likely it's worth to separate the online task (where we don't like the false alarms, which could cause extra network load) from the desktop functionality.) Many thanks for your bug report and feedback! -- You are receiving this mail because: You are the assignee for the bug.
