Lightning Components Developer Guide

What is the Lightning Component Framework?
Quick Start
Creating Components
Using Components
Communicating with Events
Creating Apps
App Overview
Designing App UI
Creating App Templates
Developing Secure Code
What is LockerService?
JavaScript ES5 Strict Mode Enforcement
DOM Access Containment
Secure Wrappers for Global References
Access to Supported JavaScript API Framework Methods Only
What Does LockerService Affect?
Disabling LockerService for a Component
Don’t Mix Component API Versions
LockerService Disabled for Unsupported Browsers
Content Security Policy Overview
Validations for Lightning Component Code
Styling Apps
Using JavaScript
JavaScript Cookbook
Using Apex
Lightning Data Service
Lightning Container
Controlling Access
Using Object-Oriented Development
Using the AppCache
Distributing Applications and Components
Debugging
Fixing Performance Warnings
Reference
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Disabling LockerService for a Component

You can disable LockerService for a component by setting API version 39.0 or lower for the component. If a component is set to at least API version 40.0, LockerService is enabled. API version 40.0 corresponds to Summer ’17, when LockerService was enabled for all orgs.

LockerService is disabled for any component created before Summer ’17 because these components have an API version less than 40.0.

Component versioning enables you to associate a component with an API version. When you create a component, the default version is the latest API version. In Developer Console, click Bundle Version Settings in the right panel to set the component version.

For consistency and ease of debugging, we recommend that you set the same API version for all components in your app, when possible.