-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
evaluateAsync fails if Promise has been polyfilled on target page #1000
Labels
Comments
ah, so the issue is this site (and presumably the others) has a DevTools checks to see if the expression is a native promise, and throws an error otherwise. Since we're just evaluating to an unguarded |
brendankenny
changed the title
evaluateAsync always throws on some sites
evaluateAsync fails if Promise has been polyfilled on target page
Nov 22, 2016
This was referenced Nov 22, 2016
patrickhulce
added a commit
to patrickhulce/lighthouse
that referenced
this issue
Nov 23, 2016
addresses GoogleChrome#1000 and GoogleChrome#976 1. Ensures all `Runtime.evaluate` calls result in the native Promise 2. Transforms all errors produced during the evaluation to a standard object that can be rejected by our driver wrapper
patrickhulce
added a commit
to patrickhulce/lighthouse
that referenced
this issue
Nov 23, 2016
addresses GoogleChrome#1000 and GoogleChrome#976 1. Ensures all `Runtime.evaluate` calls result in the native Promise 2. Transforms all errors produced during the evaluation to a standard object that can be rejected by our driver wrapper
patrickhulce
added a commit
to patrickhulce/lighthouse
that referenced
this issue
Nov 24, 2016
addresses GoogleChrome#1000 and GoogleChrome#976 1. Ensures all `Runtime.evaluate` calls result in the native Promise 2. Transforms all errors produced during the evaluation to a standard object that can be rejected by our driver wrapper
patrickhulce
added a commit
to patrickhulce/lighthouse
that referenced
this issue
Nov 24, 2016
addresses GoogleChrome#1000 and GoogleChrome#976 1. Ensures all `Runtime.evaluate` calls result in the native Promise 2. Transforms all errors produced during the evaluation to a standard object that can be rejected by our driver wrapper
patrickhulce
added a commit
to patrickhulce/lighthouse
that referenced
this issue
Nov 24, 2016
addresses GoogleChrome#1000 and GoogleChrome#976 1. Ensures all `Runtime.evaluate` calls result in the native Promise 2. Transforms all errors produced during the evaluation to a standard object that can be rejected by our driver wrapper
fixed in #1037 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
as discovered in #966, some sites will throw errors on all attempts to use
driver.evaluateAsync
with messageResult of the evaluation is not a promise
.@a-xin found a demo site which, for now at least, reliably reproduces this behavior.
The text was updated successfully, but these errors were encountered: