enter key in console and "add watch expression" performs line-break not execute #903

Open
NilsFrkal opened this Issue Aug 11, 2016 · 21 comments

Comments

Projects
None yet
@NilsFrkal

When entering commands/variables in the console (both break-point and non-break-point scenarios) or when specifying a variable under "add watch expression" the "enter" key does not execute the command/variable, but does a line-break instead. I could not find any other way to actually execute the command in the console. How can this behavior be changed or is this a bug? Thank you very much.

node-inspector version 0.12.8
nodejs 5.12.0
chrome Version 54.0.2824.0 dev-m (64-bit)

@corsen2000

This comment has been minimized.

Show comment
Hide comment
@corsen2000

corsen2000 Sep 22, 2016

Having the same issue. Any advice?

Having the same issue. Any advice?

@NilsFrkal

This comment has been minimized.

Show comment
Hide comment
@NilsFrkal

NilsFrkal Sep 22, 2016

I did not work out how to fix it. Interestingly however, I had this issue on both my desktop and my laptop. Because of an issue I had to revert back to an older backup for my desktop (this backup did not have node inspector and chrome installed). After re-installing above sws the issue did not occur anymore whilst on the laptop it still exists. If you have time try de-installing both chrome and node-inspector and re-install.

I did not work out how to fix it. Interestingly however, I had this issue on both my desktop and my laptop. Because of an issue I had to revert back to an older backup for my desktop (this backup did not have node inspector and chrome installed). After re-installing above sws the issue did not occur anymore whilst on the laptop it still exists. If you have time try de-installing both chrome and node-inspector and re-install.

@ac9

This comment has been minimized.

Show comment
Hide comment
@ac9

ac9 Oct 18, 2016

I ran into this same issue. I could not fix it by reinstalling chrome and node-inspector.
I could only fix it by rolling back to Version 51.0.2704.106 (64-bit) then disabling auto update to prevent the overwrite.

node-inspector version 0.12.8
nodejs v4.2.2
Chrome 54.0.2840.59 (64-bit)
OS X El Capitan Version 10.11.6

ac9 commented Oct 18, 2016

I ran into this same issue. I could not fix it by reinstalling chrome and node-inspector.
I could only fix it by rolling back to Version 51.0.2704.106 (64-bit) then disabling auto update to prevent the overwrite.

node-inspector version 0.12.8
nodejs v4.2.2
Chrome 54.0.2840.59 (64-bit)
OS X El Capitan Version 10.11.6

@newpost

This comment has been minimized.

Show comment
Hide comment
@newpost

newpost Oct 22, 2016

i have same issue

newpost commented Oct 22, 2016

i have same issue

@oleksiipysanko

This comment has been minimized.

Show comment
Hide comment
@oleksiipysanko

oleksiipysanko Oct 25, 2016

Same issue here

OS: macOS Sierra 10.12.1
Chrome: Version 54.0.2840.71 (64-bit)
node-inpector: 0.12.8

Note: same issue in watch - enter starts a new line

Same issue here

OS: macOS Sierra 10.12.1
Chrome: Version 54.0.2840.71 (64-bit)
node-inpector: 0.12.8

Note: same issue in watch - enter starts a new line

@ejhayes

This comment has been minimized.

Show comment
Hide comment
@ejhayes

ejhayes Oct 26, 2016

It looks like this issue might be related to a Chrome update in 54.0.2840.71. I rolled back to 51.0.2704.106 and this issue disappeared. I couldn't find a copy of Chrome version 53.0.2785.101, but I suspect that it would also work.

  • Node: 4.2.6
  • OS: El Cap 10.11.3
  • Chrome: 54.0.2840.71 (previous version 51.0.2704.106 works)

ejhayes commented Oct 26, 2016

It looks like this issue might be related to a Chrome update in 54.0.2840.71. I rolled back to 51.0.2704.106 and this issue disappeared. I couldn't find a copy of Chrome version 53.0.2785.101, but I suspect that it would also work.

  • Node: 4.2.6
  • OS: El Cap 10.11.3
  • Chrome: 54.0.2840.71 (previous version 51.0.2704.106 works)
@oleksiipysanko

This comment has been minimized.

Show comment
Hide comment
@oleksiipysanko

oleksiipysanko Oct 26, 2016

Confirmed, working fine on 51.0.2704.84 (64-bit) Chrome

Confirmed, working fine on 51.0.2704.84 (64-bit) Chrome

@Mido22

This comment has been minimized.

Show comment
Hide comment
@Mido22

Mido22 Oct 28, 2016

people, I am kinda struck, no official option to downgrade chrome in windows, (and I don't trust 3rd party stuff), so would request a higher priority to solving this bug.

Mido22 commented Oct 28, 2016

people, I am kinda struck, no official option to downgrade chrome in windows, (and I don't trust 3rd party stuff), so would request a higher priority to solving this bug.

@emimull

This comment has been minimized.

Show comment
Hide comment
@emimull

emimull Oct 29, 2016

same here. on windows. stuck.

emimull commented Oct 29, 2016

same here. on windows. stuck.

@Mido22

This comment has been minimized.

Show comment
Hide comment
@Mido22

Mido22 Oct 31, 2016

good news, found a temporary work around, retrieved chromium 53.0.2785.34, so it is kinda official/ trust-able, you can find how to retrieve older chromium versions here

Bad news, tried chrome canary v56, the issue persists in that too.

Mido22 commented Oct 31, 2016

good news, found a temporary work around, retrieved chromium 53.0.2785.34, so it is kinda official/ trust-able, you can find how to retrieve older chromium versions here

Bad news, tried chrome canary v56, the issue persists in that too.

@iamfrontender

This comment has been minimized.

Show comment
Hide comment
@iamfrontender

iamfrontender Nov 1, 2016

Look for workaround at #942

iamfrontender commented Nov 1, 2016

Look for workaround at #942

@sebastianconcept

This comment has been minimized.

Show comment
Hide comment
@devmi

This comment has been minimized.

Show comment
Hide comment
@devmi

devmi Nov 30, 2016

If you would prefer to change node-inspector code instead of downgrading Chrome, here is a nice fix (tested on Chrome 54.0.02840.98, Mac OS X, node-inspector v0.12.8)

devmi commented Nov 30, 2016

If you would prefer to change node-inspector code instead of downgrading Chrome, here is a nice fix (tested on Chrome 54.0.02840.98, Mac OS X, node-inspector v0.12.8)

@a7madgamal

This comment has been minimized.

Show comment
Hide comment
@a7madgamal

a7madgamal Dec 22, 2016

any updates on this issue? it's super critical!

any updates on this issue? it's super critical!

@neutrino84

This comment has been minimized.

Show comment
Hide comment
@neutrino84

neutrino84 Feb 4, 2017

the edit in #951 works perfectly for me, i'm pretty sure that pull request should be accepted, it's a simple change, how can it be failing a test???

the edit in #951 works perfectly for me, i'm pretty sure that pull request should be accepted, it's a simple change, how can it be failing a test???

@Lexicality

This comment has been minimized.

Show comment
Hide comment
@Lexicality

Lexicality Mar 8, 2017

Looks like the test just timed out. Anyone with write access should be able to re-run it.

Looks like the test just timed out. Anyone with write access should be able to re-run it.

abernix added a commit to meteor/docs that referenced this issue Mar 9, 2017

Add a warning about node-inspector console.
Due to a bug in `node-inspector`, pushing "Enter" after a command on the Node Inspector Console will not successfully send the command to the server.

node-inspector/node-inspector#903

This helpful tip can be reverted if/when node-inspector/node-inspector#955 lands.
@a7madgamal

This comment has been minimized.

Show comment
Hide comment
@a7madgamal

a7madgamal Apr 5, 2017

can someone please re-run the test?

can someone please re-run the test?

@kubakoz

This comment has been minimized.

Show comment
Hide comment
@kubakoz

kubakoz Jul 25, 2017

If anyone is still having this problem, I just created a solution in the form of a chrome extension.

Thanks to some insights I've read online about the nature of this issue, I made a simple "hack" that will resolve the problem.

https://chrome.google.com/webstore/detail/tizen-console-fix/hfpknnioheddhjmjhchindnmcoadmekl

Let me know if it works for you!

kubakoz commented Jul 25, 2017

If anyone is still having this problem, I just created a solution in the form of a chrome extension.

Thanks to some insights I've read online about the nature of this issue, I made a simple "hack" that will resolve the problem.

https://chrome.google.com/webstore/detail/tizen-console-fix/hfpknnioheddhjmjhchindnmcoadmekl

Let me know if it works for you!

@hustxiaoc

This comment has been minimized.

Show comment
Hide comment
@hustxiaoc

hustxiaoc Jul 26, 2017

Collaborator

This issue had been solved in #1006

Collaborator

hustxiaoc commented Jul 26, 2017

This issue had been solved in #1006

@szebenyib

This comment has been minimized.

Show comment
Hide comment
@szebenyib

szebenyib Oct 17, 2017

It still did not work for me, but @kubakoz 's plugin has helped! Many thanks 👍

It still did not work for me, but @kubakoz 's plugin has helped! Many thanks 👍

@linegel

This comment has been minimized.

Show comment
Hide comment
@linegel

linegel Apr 13, 2018

At the end, is this issue solved or not?

linegel commented Apr 13, 2018

At the end, is this issue solved or not?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment