Skip to content

Conversation

@vmeurisse
Copy link
Contributor

This caused API of page.onResourceRequested to change with phantom
1.9.0 (first argument was request, it became an array [request,
networkRequest]).

Now use fn.apply to pass arguments as they are received. This ensure
that any change in phantomjs is transparently reflected without
interference from node-phantom.

NOTE: This change the API of onError and onPrompt which where already
affected by this bug. They now get the same parameters as described on
https://github.com/ariya/phantomjs/wiki/API-Reference-WebPage.

This caused API of page.onResourceRequested to change with phantom
1.9.0 (first argument was `request`, it became an array [`request`,
`networkRequest`]).

Now use fn.apply to pass arguments as they are received. This ensure
that any change in phantomjs is transparently reflected without
interference from node-phantom.

NOTE: This change the API of onError and onPrompt which where already
affected by this bug. They now get the same parameters as described on
https://github.com/ariya/phantomjs/wiki/API-Reference-WebPage.
@alexscheelmeyer
Copy link
Owner

I like this. It is however a change that would break existing code so I will meditate some more on this.

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

Successfully merging this pull request may close these issues.

3 participants