Lightning Components Developer's Guide

Introducing the Lightning Component Framework
Quick Start
Creating Components
Working with UI Components
Using Expressions
Supporting Accessibility
Communicating with Events
Handling Events with Client-Side Controllers
Actions and Events
Component Events
Application Events
Event Handling Lifecycle
Advanced Events Example
Firing Lightning Events from Non-Lightning Code
Events Best Practices
Events Fired During the Rendering Lifecycle
Salesforce1 Events
System Events
Creating Apps
Debugging
Reference
PDF

Newer Version Available

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

System Events

The framework fires several system events during its lifecycle.

You can handle these events in your Lightning apps or components, and within Salesforce1.

Event Name Description
aura:doneRendering Indicates that the initial rendering of the root application or root component has completed.
aura:doneWaiting Indicates that the app or component is done waiting for a response to a server request. This event is preceded by an aura:waiting event.
aura:locationChange Indicates that the hash part of the URL has changed.
aura:noAccess Indicates that a requested resource is not accessible due to security constraints on that resource.
aura:systemError Indicates that an error has occurred.
aura:valueChange Indicates that a value has changed.
aura:valueDestroy Indicates that a value is being destroyed.
aura:valueInit Indicates that a value has been initialized.
aura:waiting Indicates that the app or component is waiting for a response to a server request.