Salesforce Winter '27 LWC updates and API 68.0

Winter '27 adds attributes to three LWC base components:

• **lightning-slider** gains unit, unit-position, format-number, and minimum-fraction-digits.
• **lightning-datatable** gains rowTitle for rows/errors, while its action type gains alternativeText.
• **lightning-button-icon** gains tooltip.

The release also adds the getReplicatedFieldsWithAdvancedProps wire adapter to lightning/analyticsWaveApi. Accessibility updates include larger 24px touch targets, click-to-resize datatable columns, and label wrapping at high zoom.

Use the LWC console navigation module

The console navigation update introduces lightning/platformNavigationItemApi, the LWC replacement for the Aura component lightning:navigationItemAPI. It manages navigation items in the item menu of Lightning console apps.

Its methods include:

• getNavigationItems() and getSelectedNavigationItem()
• setSelectedNavigationItem(developerName)
• focusNavigationItem() and refreshNavigationItem()

All methods return promises.

Upgrade LWC components incrementally to API 68.0

Setting apiVersion to 68.0 in a component’s .js-meta.xml picks up the latest framework features and fixes, according to the LWC API 68.0 notes. There are no version-specific behavior changes in 68.0 itself. That makes it a low-risk upgrade step, not a shortcut past intermediate versions.

For existing components:

1. Inventory apiVersion values in .js-meta.xml files. Flag components on API 58.0 or earlier.
2. Advance one API version at a time toward 68.0.
3. Fix warnings between steps before proceeding.

Components left on API 58.0 or earlier retain Summer '23 framework behavior.

Test changed interactions at existing call sites

Find existing usages of the base components covered by the release notes, then test the affected UI:

• Check touch targets on affected controls.
• Exercise click-to-resize columns in existing datatables.
• Test label wrapping at high zoom in affected layouts.

Record failures against the affected components and assign fixes.

Adopting rowTitle and alternativeText is optional. Identify where they are needed, update those row/error configurations or action-type definitions, and test the changed usages.

For a console navigation migration, find lightning:navigationItemAPI usages and map them to the new module’s methods. Handle the returned promises and test the selected console interactions.