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
Styling Apps
Using JavaScript
JavaScript Cookbook
Using Apex
Lightning Data Service (Developer Preview)
Lightning Container (Developer Preview)
Using a Third-Party Framework
Sending Messages to and from the App
Handling Errors in Your Container
Lightning Container Limits
Implement an Example
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

Lightning Container Limits

Understand the limits of lightning:container.

lightning:container has known limitations. You might observe performance and scrolling issues associated with the use of iframes. This component isn’t designed for the multi-page model, and it doesn’t integrate with browser navigation history.

If you navigate away from the page a lightning:container component is on, the component doesn’t automatically remember its state. The content within the iframe doesn’t use the same offline and caching schemes as the rest of Lightning Experience.

Content in lightning:container is served from the Visualforce domain. lightning:container can’t be used in Lightning pages that aren’t served from the Lightning domain, such as Visualforce pages (using Lightning Components for Visualforce) or Community Builder. These restrictions allow lightning:container to comply with LockerService security, and might change in future releases.