New and Changed Lightning Events

Lightning events facilitate communication between components and increase interactivity in your apps.

New Events

The following event is new.

A lightningcommunity:deflectionSignal event is fired when a community user is going through a process to solve an issue, and then views a deflection item that could potentially resolve their issue early. For example, a user is filling out a form to create a case in a community when they see a recommended useful article. The article proves helpful, and the community user no longer needs to file a case with support. This event is available only in Lightning communities.

Deprecated Events

These application events can be fired by every component in your app. Unless your component is running in complete isolation in a standalone app and not included in complex apps, such as Lightning Experience or the Salesforce mobile app, the container app can trigger your event handler multiple times. This behavior makes it difficult to handle each event appropriately.

The following system events are deprecated.

Use the render event on your application or component instead.
To determine when an action is complete, use the response status in an action’s callback instead.
Execute logic after queueing an action instead of using this event. A component is waiting for a response for an action until the action’s callback is invoked.

The force:navigateToComponent event is deprecated. This event base64 encodes the component, which leaves it susceptible to cross-site scripting attacks. Instead, implement the lightning:isUrlAddressable interface on the target component and navigate to the component using the lightning:navigation component with the standard__component page type. This process generates a route in the format /cmp/{componentName}?myAttr=attrValue. This workflow opens tabs and subtabs to custom components without exposing security concerns.