How to control lightning locker for Lightning components?
To control whether Lightning Locker is enforced for components installed from a managed package: From Setup, enter Lightning Components in the Quick Find box, and then select Lightning Components. installed from a managed package. Note: The checkbox is only visible when the critical update is activated.
When to deactivate the Lightning locker critical update?
If you deactivate the Lightning Locker critical update before the Spring ’17 release, the stricter CSP won’t be applied. In Summer ’17, Lightning Locker will be auto-activated for all orgs with no option to disable. To control whether Lightning Locker is enforced for components installed from a managed package:
When did the Lightning container component come out?
The Lightning Container Component is in Developer Preview in Spring ’17. The Lightning Container Component can be used to sandbox components or apps built with libraries that don’t run with LockerService.
Which is the isolation mechanism for the Lightning component framework?
The Lightning Component Framework comes with two isolation mechanisms: LockerService and the Lightning Container Component (in Developer Preview in Spring ’17). LockerService is the primary and preferred isolation mechanism for the Lightning Component Framework.
When is lightning locker auto activated for all Orgs?
In Summer ’17, Lightning Locker will be auto-activated for all orgs with no option to disable. To control whether Lightning Locker is enforced for components installed from a managed package:
When does the CSP apply for lightning locker?
If you have a sandbox or Developer Edition org with the Lightning Locker critical update activated, the stricter CSP will apply when Spring ’17 rolls out. If you deactivate the Lightning Locker critical update before the Spring ’17 release, the stricter CSP won’t be applied.