Page.navigate hangs with angular application

Component	Version
Operating system	Manjaro Linux
Node.js	8.9.4
Chrome/Chromium/…	64.0.3282.140
chrome-remote-interface	0.25.5

Is Chrome running in a container? NO

When navigating in an angular application, the call to Page.navigate hangs forever. I bundled a minimal script that triggers this bug: https://gist.github.com/m-rousse/de42a69db1405d82a919689778329c12

If I add a void Page.navigate({url: 'http://localhost:8123/index.html#!/next'}) before line 10 of main.js, the call is successful and the navigation is resumed. If I reload the page in the browser (using F5), it does also resume the script.

While debugging, I noticed that the Page.navigate command is successfully sent but no response is received. (cf. image)

I have this same bug at other calls in my code, and noticeably when using the Debugger.resume command, and the only way out of this being calling the Page.navigate once again.

This might be a problem of chrome itself so I crossposted this issue on the chromium bugtracker (cf. issue)

[paulirish]

768961 - [regression] Page.navigate protocol method doesn't resolve immediately - chromium

😃

[cyrus-and]

You’re welcome!

For the second bug, I will report it to the chromium team.

Feel free to post here the follow up so to help others.