Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certain Shortcuts No Longer Work After using "g" to Jump #81

Closed
kory-smith opened this issue Jul 25, 2019 · 3 comments
Closed

Certain Shortcuts No Longer Work After using "g" to Jump #81

kory-smith opened this issue Jul 25, 2019 · 3 comments

Comments

@kory-smith
Copy link
Contributor

Ever since Todoist version 959, there's some strange behavior. After using the g key to jump to a new project, hitting keys like T (note the capital) or v where you type in the command no longer work. They still bring up a menu, but you cannot type in them like you should be. This gets fixed once you refresh the page but the behavior repeats itself after another g jump.

I'm on Chrome 72 if that helps.

@ErikOsterud
Copy link

Noticed a similar issue with the shift+3 (delete) command. With the new version it works a time or two, but then the page needs to be refreshed to work again.

@mgsloan
Copy link
Owner

mgsloan commented Jul 25, 2019

Hey, thanks for reporting these issues!

I just started seeing these problems today too, will hopefully take a look at it this evening. Traveling this weekend and packing this evening so unfortunately there's a possibility I won't get around to fixing it till early next week.

mgsloan added a commit that referenced this issue Jul 26, 2019
Looks like Todoist now sometimes re-creates the #editor DOM node, so
instead now watching its parent, #content
mgsloan added a commit that referenced this issue Jul 26, 2019
@mgsloan
Copy link
Owner

mgsloan commented Jul 26, 2019

I didn't figure out why exactly T and v started misbehaving. I think I found a fix though and released it in version 59. Does the issue appear to be fixed? Please comment / reopen if not.

I did notice another symptom, which is that the cursor isn't visible after switching projects. The mechanism that notices when the cursor isn't on anything broke! It expected that a DOM element with id editor would never be re-created, but it appears that is no longer true.

@mgsloan mgsloan closed this as completed Jul 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants