It used to be that after marking an item complete (Space or Shift+Space), the next item in the list (that took its...
It used to be that after marking an item complete (Space or Shift+Space), the next item in the list (that took its place) would be selected, but now it is selecting the last item in the list. This seems like a bug.
Hi, could you please check how it works on https://beta.checkvist.com? I hope we have fixed the problem there. Thanks!
ReplyDeletebeta.checkvist.com - Checkvist: Keyboard-centric outliner and task manager
No, it's the same.
ReplyDeleteHello Kyle,
ReplyDeleteDoes it reproduce on all your lists? Could you give an ID of the list where this problem reproduce, so I could take a closer look?
Thanks,
It happens with all of my lists. I'm using Firefox on Windows 10, in case it matters.
ReplyDeleteStill cannot reproduce it :( Could you please try opening Checkvist in a private Firefox window? I suppose some web extension in the Firefox may be a cause of such behaviour.
ReplyDeleteI'm getting the same behavior in Firefox (with addons disabled), Chrome, IE, and Edge. In some cases, it selects the last item in the list, and in other cases it selects the parent item, but never the item that replaced the completed/invalidated item in the list. I do have Hide Completed and Move Completed Down checked.
ReplyDeleteAha, move completed down is the cause. Thanks a lot for the help, will try to fix it ASAP
ReplyDelete.
Hello again, could you please check the beta site again, I believe I've fixed the issue there. The production site will be updated later, the next week most likely.
ReplyDeleteThanks for the help!
It's different, but it is selecting the previous item in the list (the one above the completed item), rather than the one that moved into the location of the one that was completed.
ReplyDeleteHello Kyle A, you're right, that's a bit confusing. I'll try to improve it further.
ReplyDeleteThanks!
Any progress?
ReplyDeleteHello Kyle A, please check how it now works on https://beta.checkvist.com, I hope I've fixed it finally.
ReplyDeleteYes, and that operation also feels snappier now. Thanks!
ReplyDeleteThanks!
ReplyDelete