Skip to content
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.

remoteDebuggerPort not respected #31

Closed
tecfu opened this issue Apr 18, 2015 · 3 comments
Closed

remoteDebuggerPort not respected #31

tecfu opened this issue Apr 18, 2015 · 3 comments

Comments

@tecfu
Copy link
Contributor

tecfu commented Apr 18, 2015

I'm attempting to pass the following flags to phantomjs via phridge:

phridge.spawn({
  webSecurityEnabled : false,
  remoteDebuggerPort : 8888,
  ignoreSslErrors : true,
  remoteDebuggerAutorun : true
})

remoteDebuggerPort does not behave the same as --remote-debugger-port=8888, i.e. :

phantomjs --remote-debugger-port=8888 somfile.js

Allows one to open up a debugging session at 127.0.0.1:8888 in chrome/chromium.
These debugging sessions don't fire in phridge, however.

Workaround?

@tecfu
Copy link
Contributor Author

tecfu commented Apr 18, 2015

Ubuntu 14.04
Chrome Version 41.0.2272.76 (64-bit)
phridge 1.0.8
node v0.12.2

@tecfu
Copy link
Contributor Author

tecfu commented Apr 18, 2015

This option simply hasn't been added in the phantomjs source. See:
https://github.com/ariya/phantomjs/blob/master/src/config.h
ariya/phantomjs#12149 (comment)

Also note that phantomjs has 1470 open issues as of this posting, and that other JSON config options fail as well. i.e. :
ariya/phantomjs#13115

I think I'm going to write a patch that uses the CLI style args instead.

@tecfu
Copy link
Contributor Author

tecfu commented Apr 18, 2015

Patched and created pull request.

See: #32

@tecfu tecfu closed this as completed Apr 28, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant