Apex Code Development You need to sign in to do that
Don't have an account?
Stephen Jenkins 22 Enable Secure Static Resource for Lightning Components - Winter '21 (enabled) / Spring '21 (Enforced)
Does anyone have insight regarding the obvious Catch-22 Salesforce is setting up:
Enable Secure Static Resource for Lightning Components - Winter '21 (enabled) / Spring '21 (Enforced)
From the Winter '21 Release Notes (https://releasenotes.docs.salesforce.com/en-us/winter21/release-notes/rn_lc_secure_static_resources_update.htm):
"To improve security, this update serves all static resources from the visualforce domain instead of the lightning domain. This change prevents a script included in a static resource from accessing the document in the lightning domain due to the same-origin security policy."
From the Lightning Aura Components Developer Guide (https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/js_libs_platform.htm):
"The framework’s content security policy mandates that external JavaScript libraries must be uploaded to Salesforce static resources. For more information on static resources, see “Static Resources” in the Salesforce online help."
Here is a Known Issue (https://trailblazer.salesforce.com/issues_view?id=a1p4V000001JipTQAS) related to the topic.
My question to this forum is:
Have you been successful in implementing external libraries with the Winter '21 update enabled? If so, are you willing to share?