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
Salesforce Lightning CLI
Styling Apps
Using JavaScript
JavaScript Cookbook
Using Apex
Lightning Data Service (Beta)
Lightning Container (Developer Preview)
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

What Does LockerService Affect?

Find out what’s affected and what’s not affected by LockerService.
LockerService enforces security and best practices for custom Lightning components you use in:
  • Lightning Experience
  • Salesforce1
  • Lightning Communities
  • Standalone apps that you create (for example, myApp.app)
  • Any other app where you can add a custom Lightning component, such as Salesforce Console in Lightning Experience
  • Lightning Out
LockerService doesn’t affect the following except for usage of Lightning components in Visualforce in these contexts:
  • Salesforce Classic
  • Visualforce-based communities
  • Any apps for Salesforce Classic, such as Salesforce Console in Salesforce Classic