auto-save for a task description sometimes moves the cursor back to the start of the textbox #1850
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1850
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I am using v0.18.1 of both the frontend and the backend.
When editing a task's description in either Safari v13.1.2 (macos High Sierra) or Chrome 94 (latest), I sometimes experience annoying behaviour with the auto-save feature. When the autosave completes, it will move the text cursor to the start of the textbox. This means when I continue typing, the text appears to be at the front. Sometimes the autosave even gets into a loop, where it switches between text I have typed at the start of the description and where I was typing beforehand.
the problem seems more likely to occur if I start typing while the auto-save is in progress.
It would be great if there was an option in the user settings to disable this feature. I don't have any issues when editing comments, as they don't have the auto-save functionality.
I wouldn't even call that a feature, thats a bug.
Just to be sure, that only happens when editing the task description?
We plan to replace the editor in general with something else (#781) which will hopefully make that problem go away.
Yes, definitely a bug. And yes, I've only seen this behaviour when editing task description, due to auto-save.
It seems that the autosaving is sometimes racing with itself. There are a couple of points I've noticed:
@freaktechnik Thanks for your observations.
I think the easiest way to fix that would be to either
A combination of the last two is probably the way to go.
It sounds a bit like the speed of internet connection plays a role here. Did you check that, maybe with the connection emulator in chrome?
To avoid what I'm seeing if anything the save would have to be faster, since what happens is
Making the network slower would only make this worse.
Is this still an issue?