[Feature Request]: include selected view in `UserSettingsItem` `selection-change` event

[Lukas742]

Feature Request Description

Currently, the selection-change event of the UserSettingsItem component doesn't include the selected view when navigating via the back button. event.detail.view only holds the view before navigation. In React for example, this is inconvenient, because it's typical to fully control a component there.

Here you can find an example that shows the current behavior: https://stackblitz.com/edit/github-hygzc2rt?file=index.html,main.js,package.json

2025-07-01_09-56-26.mp4

Proposed Solution

Include a selectedView (or similar) property in the event details, which points to the element after selection.

Proposed Alternatives

No response

Organization

UI5WCR

Additional Context

No response

Priority

None

Privacy Policy

• I’m not disclosing any internal or sensitive information.

[yanaminkova]

Hello @SAP/ui5-webcomponents-topic-skr,

Can you take a look at this feature request?

Thanks and regards,
Yana

[adrian-bobev]

Hello @Lukas742,

As we discussed on the phone, the current control design does not require explicitly passing the currently selected view when the back button is clicked. This is because the back button simply clears the selected property of the current view, effectively reverting the selection to the primary view.

The control assumes one primary view and one or more secondary views, so you can rely on the back button always returning to the primary view by default.

Additionally, the selection-change event is cancelable. By preventing the default behavior, you can programmatically select any view—not just the primary one. This enables more advanced navigation scenarios, such as navigating through a chain of views and customizing the back button behavior accordingly. Including the currently selected view in the event parameters gives you full control over the navigation logic, allowing you to determine the current state and navigate as needed.

P.S. As discussed, we agree it would be helpful to provide a more comprehensive example on our side to better demonstrate the full flexibility of this approach.

Best regards,
Adrian

[github-actions]

This issue has been closed. To reopen, just leave a comment!