When adding new labels, auto-complete window won't close.
If I try to add a NEW label for a todo and the auto-complete box pops up, it says press ESC to close the window. When I press ESC the Todoist extension/window closes. Because the auto-complete window blocks the SAVE button, it makes adding new labels very annoying (clicking off the current todo to close the auto-complete window, then clicking save).
How are use accessing Todoist (which platform: web (which browser?); Windows application; plugin)?
I just created a new label (using Todoist on the Web using Chrome one a Windows 7 PC) and once the AutoComplete recognized this was a new label, I clicked ESC and nothing closed (except the AutoCompleet window) and I could just press ENTER to save the Task.
Chrome Version 30.0.1599.101 m
Chrome Extension: Todoist: To-Do list and Task Manager 6.0
When adding the label, I'm clicking on the LABEL icon first, then typing the label. I don't seem to have the same problem if adding the label at the beginning of the todo (by just typing @something). As soon as I type a SPACE after the label, auto-complete disappears on its own.
I can't fully reproduce this issue. When I hit the SPACE after the label - the auto-complete closes. When I hit ESC - it also closes and in both cases I can then save the task with ENTER.
Please clarify how exactly can you reproduce the situation in which the label auto-complete window won't close?
Click a task to edit, click the label icon, press ESC.
Todoist completely closes.
This is only happening in Windows. I tested on my MacBook and can't reproduce.
So this is only happening within the extension? I can only reproduce it there, it works correctly on the web-version through Chrome.
I've passed it to the developers, if you're also experiencing this within the web-app, please let me know.
In can reproduce it on Firefox 25, Linux, using the normal web interface, i.e. no extension. The auto-complete window does *not* close on ESC and Enter. Space works. Hope this helps.
Thank you for your report, I've passed it to the developers and we'll look into it.