New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 743611 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit 29 days ago
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

headless chrome network.enable() wasn't found

Reported by ylsc...@gmail.com, Jul 15 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.104 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. use chrome-remote-interface, "version": "0.24.2",url:https://github.com/cyrus-and/chrome-remote-interface
2. run the demo:
const CDP = require('chrome-remote-interface');

CDP((client) => {
    // extract domains
    const {Network, Page} = client;
    // setup handlers
    Network.requestWillBeSent((params) => {
        console.log(params.request.url);
    });
    Page.loadEventFired(() => {
        client.close();
    });
    // enable events then start!
    Promise.all([
        Network.enable(),
        Page.enable()
    ]).then(() => {
        return Page.navigate({url: 'https://github.com'});
    }).catch((err) => {
        console.error(err);
        client.close();
    });
}).on('error', (err) => {
    // cannot connect to the remote endpoint
    console.error(err);
});
3. Error: 'Network.enable' wasn't found
Message:
 at D:\git\pageScreenshot\node_modules\chrome-remote-interface\lib\chrome.js:
90:30
    at Chrome.handleMessage (D:\git\pageScreenshot\node_modules\chrome-remote-in
terface\lib\chrome.js:289:13)
    at WebSocket.<anonymous> (D:\git\pageScreenshot\node_modules\chrome-remote-i
nterface\lib\chrome.js:266:27)
    at emitTwo (events.js:106:13)
    at WebSocket.emit (events.js:194:7)
    at Receiver._receiver.onmessage (D:\git\pageScreenshot\node_modules\ws\lib\W
ebSocket.js:143:54)
    at Receiver.dataMessage (D:\git\pageScreenshot\node_modules\ws\lib\Receiver.
js:385:14)
    at Receiver.getData (D:\git\pageScreenshot\node_modules\ws\lib\Receiver.js:3
33:12)
    at Receiver.startLoop (D:\git\pageScreenshot\node_modules\ws\lib\Receiver.js
:155:19)
    at Receiver.add (D:\git\pageScreenshot\node_modules\ws\lib\Receiver.js:134:1
0)
  response: { code: -32601, message: '\'Network.enable\' wasn\'t found' } }

What is the expected behavior?

What went wrong?
run the demo error

Did this work before? N/A 

Chrome version: 59.0.3071.104  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 
error message.png
44.0 KB View Download
Components: -Internals>Network Internals>Headless
Owner: dvallet@chromium.org
Thanks for the report
Sorry but I cannot reproduce on Windows 10. 

Can you confirm that it works for non headless Chrome?
Status: Assigned (was: Unconfirmed)
Labels: Needs-Feedback

Sign in to add a comment