Skip to content
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

downloadedUnhandled rejection promise: window.requestAnimationFrame is not a function #1144

Closed
pparmentier opened this issue Jun 21, 2018 · 2 comments

Comments

@pparmentier
Copy link

pparmentier commented Jun 21, 2018

Please tell us about your:

Environment

  • sonarwhal version = 1.11.2
  • Node.js version = v8.9.4
  • npm version = 6.1.0

sonarwhal configuration

sonarwhal’s configuration
{
    "extends": ["web-recommended"],
}

URL for which sonarwhal failed

Output

Please include the raw output generated by sonarwhal, or if possible,
the raw output from running sonarwhal in debug mode: sonarwhal --debug <URL>.

sonarwhal’s raw output

- https://www.chanel.com/ … e-onechanel/onechanel.js downloadedUnhandled rejection promise:
    uri: undefined
    message: window.requestAnimationFrame is not a function
    stack:
TypeError: window.requestAnimationFrame is not a function
    at https://www.chanel.com/_ui/responsive/theme-onechanel/onechanel.js:1:11025
    at new Promise (<anonymous>)
    at e.value (https://www.chanel.com/_ui/responsive/theme-onechanel/onechanel.js:1:10994)
    at https://www.chanel.com/_ui/responsive/theme-onechanel/onechanel.js:1:13141
    at https://www.chanel.com/_ui/responsive/theme-onechanel/onechanel.js:1:40915
    at Array.forEach (<anonymous>)
    at s.trigger (https://www.chanel.com/_ui/responsive/theme-onechanel/onechanel.js:1:40895)
    at s.show (https://www.chanel.com/_ui/responsive/theme-onechanel/onechanel.js:1:40468)
    at e.value (https://www.chanel.com/_ui/responsive/theme-onechanel/onechanel.js:1:12433)
    at https://www.chanel.com/_ui/responsive/theme-onechanel/onechanel.js:1:13784

@molant
Copy link
Member

molant commented Aug 8, 2018

Similar to #521. We should be capable of fixing it once we have #163 (which we should be capable of doing in the next release of jsdom)

@molant
Copy link
Member

molant commented Aug 8, 2018

Closing in favor of #1223

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants