LWR Template Limitations

Unsupported Features and Settings

The following items are unavailable.

• Several of the default components and pages that you get with Aura templates
• Several preconfigured standard pages, such as Account Management, used when creating custom pages
• The default Navigation Menu component, although you can build your own
• Progressive rendering
• Out-of-the-box themes and theme management
• Right-to-left languages in standard components
• Template, page, and theme export and Lightning Bolt Solutions
• Template-level accessibility features, such as a skip link
• App-level events that you get with Aura templates, although you can use CustomEvent
• Some base components and features from the Lightning Component Library
• Some properties in the @salesforce/i18n module
• Mobile and value providers such as $Browser
• The pageAccess property in the ExperienceBundle metadata type.
• Salesforce Community Page Optimizer
• Surveys

Experience Workspaces Limitations

Only the Administration, Builder, Dashboards, and Guided Setup workspaces are available.

Experience Builder Limitations

• In the toolbar, the Undo and Redo buttons and some Help options are unavailable.
• In the Theme panel, branding sets, theme settings, and the CSS editor are unavailable. For alternative solutions, such as creating section palettes or adding style sheets to the head markup, see Brand Your LWR Site.
• When working with components, some hover actions and some of the action menu options in the property editor are unavailable.
• When you modify records while previewing your site in Experience Builder, you can sometimes see stale record data if you navigate to a previous page. To fix this issue, refresh your browser.
• Experience admins can't access record pages in Experience Builder for objects that they don't have access to.

Lightning Web Security Limitations

Instead of Lightning Locker, LWR sites use Lightning Web Security (LWS), the new security architecture for Lightning web components. LWS in LWR sites currently includes some limitations.

• Scripts loaded through lightning/platformResourceLoader run in an LWS sandbox. To use lightning/platformResourceLoader in an LWR site, you must implement your own loadScript function. See an example within codeSamples/resourceLoader in the code sample files.
• The await and async expressions aren’t supported. Instead, use promises, or pre-compile the code using Babel to replace await and async expressions with equivalent supported code.
• The following properties are currently unsupported:
  • document.domain
  • document.location
  • window.location
  • window.top

Asset Files in Sandbox Limitations

Full and Partial Copy sandboxes can support asset files along with other content entities. Asset files are unsupported in Developer and Developer Pro sandboxes. When defining the sandbox template for Full and Partial Copy sandboxes, make sure to select Content Body in the template also.

For unsupported sandboxes, if your site contains a Lightning web component with a @salesforce/contentAsset reference, the reference breaks in the site on the sandbox org. In LWR sites, the component can’t render, and you can’t publish the site unless you delete the component from the page or else remove the asset reference from the component. In Aura sites, the imported reference resolves to an invalid URL.