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

Not working at all #18

Closed
benadamstyles opened this issue Jul 19, 2016 · 3 comments
Closed

Not working at all #18

benadamstyles opened this issue Jul 19, 2016 · 3 comments

Comments

@benadamstyles
Copy link

Atom package atomic-chrome version: 0.3.0
Atomic Chrome extension version: 0.2.6

Clicking the browser button does nothing. Atom is open already. I tried inspecting the extension's background page via Chrome extension manager developer mode and the devtools view opens but there is nothing there, no console logs of any kind, and I am unable to use the console to run any javascript, pressing enter in the console just clears the input. It feels like the extension just isn't initialising. Any ideas?

@danhper
Copy link
Owner

danhper commented Jul 19, 2016

Hi, thanks for reporting.

What page were you using when you tried the plugin?
There could be some sites for which it just does not work,
although it seems weird that no window gets opened in Atom.
Do you get the same behavior with GitHub issues?

Also, could it be that you have another instance of Atom running somewhere?

If it does not seem to work, could you please try the following:

$ npm install -g wscat
$ wscat -c ws://localhost:64292
> {"type": "register", "payload": {"extension": ".md", "title": "Hello", "text": "some text"}}

This should open a new tab in Atom with written "some text" in it.
Could you let me know if this works or not please?

Thank you!

@benadamstyles
Copy link
Author

Hey man I am really sorry but I just restarted my mac and it is working again. I should have tried this before posting this issue. wscat is doing what you said it should. I'm going to close this and assume that as the extension wasn't initialising at all, this was a chrome issue and nothing to do with your code. Thanks for the detailed response and sorry for wasting your time!

@danhper
Copy link
Owner

danhper commented Jul 19, 2016

No problem! Thanks for the feedback 😃

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

2 participants