Visualforce Developer Guide
jNote: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
Considerations and Limitations
Keep these considerations and limitations in mind when working with Lightning message
service in Visualforce.
- Considerations
- Lightning message service doesn’t work for Visualforce’s sforce.one library when pages are loaded in the Chatter Publisher that uses <chatter:feed showPublisher="true"/>. Use the native Lightning Publisher instead.
- Lightning message service doesn’t work in Visualforce pages that are included in Lightning Experience via iframes, including <wave:dashboard>, <apex:iframe>, and the standard HTML <iframe> tag. Instead, add Visualforce pages through the Lightning App Builder or as a utility bar item.
- Visualforce supports only Lightning Message Channels where isExposed is true. For more information about LightningMessageChannel, see the Metadata API Developer Guide.
- Lightning message service doesn’t work in Salesforce Classic or when previewing Visualforce from Setup.
- Limitations
- The lightning message service supports only these
experiences.
- Lightning Experience standard navigation
- Lightning Experience console navigation
- Salesforce mobile app for Aura and Lightning Web Components, but not for Visualforce pages
- Lightning components used in Experience Builder sites. Support for Experience Builder sites is beta.