Lightning Aura Components Developer Guide

What Is the Lightning Component Framework?
Quick Start
Creating Components
Using Components
Communicating with Events
Communicating Across the DOM with Lightning Message Service
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
Select the Locker API Version for an Org
Disable Lightning Locker for a Component
Don’t Mix Component API Versions
Lightning Locker Disabled for Unsupported Browsers
Content Security Policy Overview
Using JavaScript
Working with Salesforce Data
Testing Components with Lightning Testing Service
Debugging
Performance
Reference
PDF

Newer Version Available

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

What Does Lightning Locker Affect?

Find out what’s affected and what’s not affected by Lightning Locker.
Lightning Locker enforces security and best practices for custom Lightning components you use in:
  • Lightning Experience
  • Salesforce mobile app
  • Experience Builder sites
  • Flows
  • Standalone apps that you create (for example, myApp.app) to run in Salesforce Classic or Lightning Experience
  • Any other app where you can add a custom Lightning component, such as Salesforce Console in Lightning Experience
  • Lightning Out
  • Visualforce pages in Salesforce Classic
  • Visualforce-based sites

Lightning Locker doesn’t affect environments where you don’t use custom Lightning components.