Lightning Aura Components Developer Guide

What Is the Lightning Component Framework?
Quick Start
Creating Components
Using Components
Communicating with Events
Creating Apps
Styling Apps
Developing Secure Code
What is Lightning Locker?
JavaScript Strict Mode Enforcement
DOM Access Containment
Secure Wrappers
eval() Function is Limited by Lightning Locker
MIME Types Permitted
Access to Supported JavaScript API Framework Methods Only
What Does Lightning Locker Affect?
Lightning Locker Tools
Disabling Lightning Locker for a Component
Don’t Mix Component API Versions
Lightning Locker Disabled for Unsupported Browsers
Content Security Policy Overview
Freeze JavaScript Prototypes
Using JavaScript
Working with Salesforce Data
Using Apex
Testing Components with Lightning Testing Service
Debugging
Performance
Reference
PDF

Newer Version Available

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

Disabling Lightning Locker for a Component

You can disable Lightning Locker 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, Lightning Locker is enabled. API version 40.0 corresponds to Summer ’17, when Lightning Locker was enabled for all orgs.

Lightning Locker 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.