Colabtools: Keyboard shortcuts not working in Google Colab when Evernote webclipper extension is installed

Created on 13 Nov 2019  Â·  13Comments  Â·  Source: googlecolab/colabtools

Bug report for Colab: http://colab.research.google.com/.

For questions about colab usage, please use stackoverflow.

  • Describe the current behavior:
    Keyboard shortcuts like Ctrl+M+D or Shift+Enter aren't working. I am using Google Chrome.
    Even Ctrl+A doesn't work, Ctrl+C and Ctrl+V work though.
    I tried it in Microsoft Edge and it didn't work there too.
    I tried these shortcuts on other websites and they worked, so it's not a keyboard issue.
    I restarted my laptop but that didn't work either.

  • Describe the expected behavior:
    Shortcuts like Ctrl+M+D should delete current cell but isn't doing anything.

  • The web browser you are using (Chrome, Firefox, Safari, etc.):
    Chrome, tried it in Edge and that didn't work too.

  • Link to self-contained notebook that reproduces this issue
    (click the Share button, then Get Shareable Link):
    I tested it by sharing the said notebook to my friends, the shortcuts worked for them.

Is it some sort of setting I don't know that I should turn it on? I searched through all the settings but couldn't find anything.

Most helpful comment

If you are experiencing this, what operating system keyboard layout are you using?

Can you try using the old editor at: https://colab.research.google.com/notebooks/editor_details.ipynb

All 13 comments

Hello,
It's possible that at some point you changed your default keyboard shortcut settings. Try going to Tools->Keyboard Shortcuts and click "Restore Defaults" to restore the default keyboard shortcuts.

Hello,
It's possible that at some point you changed your default keyboard shortcut settings. Try going to Tools->Keyboard Shortcuts and click "Restore Defaults" to restore the default keyboard shortcuts.

Hi... Thanks for the reply. I did try restoring it to default and it didn't work. What worked is changing the shortcut to something else. But I want the shortcuts to work in default.
Thanks.

Do you know what keyboard layout you are using?

Hi I have the same issue since yesterday. And my friends are having this problem occasionally as well. Please fix it! Thanks!!!

If you are experiencing this, what operating system keyboard layout are you using?

Can you try using the old editor at: https://colab.research.google.com/notebooks/editor_details.ipynb

If you are experiencing this, what operating system keyboard layout are you using?

Can you try using the old editor at: https://colab.research.google.com/notebooks/editor_details.ipynb

Hi. I'm using Windows 10 OS and US Keyboard layout.

Disabling the new features worked! Keyboard shortcuts started working when I went back to 'Classic' in the features section. Wonder why keyboard shortcuts aren't working in the new editor.

Thanks!

I remember seeing similar behavior on one of my colleagues' computer to
whom I recommended switching to a new Colab editor :) Also with Windows 10
OS and US Keyboard layout (which is strange because I have a computer with
Windows 10 OS and US keyboard layout and don't experience any such issues).
So this seems to happen from time to time...

On Wed, Nov 13, 2019 at 10:13 PM OV Nikhilesh notifications@github.com
wrote:

If you are experiencing this, what operating system keyboard layout are
you using?

Can you try using the old editor at:
https://colab.research.google.com/notebooks/editor_details.ipynb

Hi. I'm using Windows 10 OS and US Keyboard layout.

Disabling the new features worked! Keyboard shortcuts started working when
I went back to 'Classic' in the features section. Wonder why keyboard
shortcuts aren't working in the new editor.

Thanks!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googlecolab/colabtools/issues/858?email_source=notifications&email_token=AIFIU25ZJZNESKWMA524XW3QTS66XA5CNFSM4JM3IM4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEAN2AQ#issuecomment-553704706,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIFIU26WX3IQK5SZH6JPCK3QTS66XANCNFSM4JM3IM4A
.

--
"Intelligence is the ability to adapt to change." - Stephen Hawking.

I remember seeing similar behavior on one of my colleagues' computer to whom I recommended switching to a new Colab editor :) Also with Windows 10 OS and US Keyboard layout (which is strange because I have a computer with Windows 10 OS and US keyboard layout and don't experience any such issues). So this seems to happen from time to time...

The new editor was working for me too for many months and suddenly out of the blue this issue started 2 days ago. It's a browser issue definitely as I am able to use the shortcuts with my account on another device. Hope it can be fixed soon.

What browser+version? Does it repro in an incognito window?

What browser+version? Does it repro in an incognito window?

I am using Google Chrome Version 78.0.3904.97 (Official Build) (64-bit). No it doesn't reproduce in an incognito window.

I tried clearing cookies and it didn't work. Restarting the browser didn't work either.

Not being able to reproduce in an incognito window points at a chrome
extension. Can you try disabling chrome extensions to identify which one
might be causing the issue?

On Thu, Nov 14, 2019, 00:25 OV Nikhilesh notifications@github.com wrote:

What browser+version? Does it repro in an incognito window?

I am using Google Chrome Version 78.0.3904.97 (Official Build) (64-bit).
No it doesn't reproduce in an incognito window.

I tried clearing cookies and it didn't work. Restarting the browser didn't
work either.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googlecolab/colabtools/issues/858?email_source=notifications&email_token=AJCRJKQZ7JXR4IDZ4ZOWWHDQTUDPDA5CNFSM4JM3IM4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEA776A#issuecomment-553779192,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJCRJKQ7MN4DWBETMRZ575TQTUDPDANCNFSM4JM3IM4A
.

--
You received this message because you are subscribed to the Google Groups
"colaboratory-team" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/google.com/d/msgid/colaboratory-team/googlecolab/colabtools/issues/858/553779192%40github.com
https://groups.google.com/a/google.com/d/msgid/colaboratory-team/googlecolab/colabtools/issues/858/553779192%40github.com?utm_medium=email&utm_source=footer
.

Not being able to reproduce in an incognito window points at a chrome extension. Can you try disabling chrome extensions to identify which one might be causing the issue?
…
On Thu, Nov 14, 2019, 00:25 OV Nikhilesh @.> wrote: What browser+version? Does it repro in an incognito window? I am using Google Chrome Version 78.0.3904.97 (Official Build) (64-bit). No it doesn't reproduce in an incognito window. I tried clearing cookies and it didn't work. Restarting the browser didn't work either. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#858?email_source=notifications&email_token=AJCRJKQZ7JXR4IDZ4ZOWWHDQTUDPDA5CNFSM4JM3IM4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEA776A#issuecomment-553779192>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJCRJKQ7MN4DWBETMRZ575TQTUDPDANCNFSM4JM3IM4A . -- You received this message because you are subscribed to the Google Groups "colaboratory-team" group. To unsubscribe from this group and stop receiving emails from it, send an email to *@.* To view this discussion on the web visit https://groups.google.com/a/google.com/d/msgid/colaboratory-team/googlecolab/colabtools/issues/858/553779192%40github.com https://groups.google.com/a/google.com/d/msgid/colaboratory-team/googlecolab/colabtools/issues/858/553779192%40github.com?utm_medium=email&utm_source=footer .

Thanks a lot! Evernote web clipper extension was causing the issue. It's fixed now.

@NikhileshOV thanks for tracking that down!

Was this page helpful?
0 / 5 - 0 ratings