Before summer 17, the jquery version 2.2.4 was working well with locker service. Now, with summer 17, we have locker service enabled automatically. With this, if we update our components to version 40, then again the jquery is not working with the locker service. Has anyone encountered this issue? Does anyone have a solution to this issue?

Below is the error screen short, enter image description here

  • 1
    What do you mean by "not working"? Is there a specific method or operation that's not working, or an error message? Jun 27, 2017 at 15:06
  • @Florissant53 i have added error screen short in main question. Thanks! Jun 27, 2017 at 16:31
  • @thoriyas Can you file a case with salesforce and provide login access to your org? From just looking at the screenshot it seems to be a CSP issue. It isn't clear how Locker Service would cause it. Locker Service doesn't control the CSP of the page, lightning platform does. Jun 28, 2017 at 17:20
  • @RaviJayaramappa FYI We have used the lightning component using lightning out app in vf page and that Vf page we have put inside the record detail page. Jun 29, 2017 at 5:32
  • @RaviJayaramappa We have filed the case for this issue with Support · Case 16805352 Jul 3, 2017 at 9:21

1 Answer 1


Take a look at this thread, and see if the suggestions there help. Looks like there might be a couple suggestions:

  1. Use a later version of jQuery (3.2.1 is suggested), as version 2.2.4 might try modifying the DOM out of scope (whatever that means, I'm not that familiar with cross domain errors).

  2. Downgrade the API version. Although I think that disables LockerService, and I do all my development with it enabled, so I personally wouldn't do that.

Cross-Origin Frame Error in Lightning Component embedded in Salesforce Console

Hope this info helps!


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.