Add possibility to change click-behaviour
Hi,
maybe I missed it, but it looks like there is no way to prevent the breadcrumb (and following items) from disappearing after a click. My situation is as following:
<NavigationLock ConfirmExternalNavigation="true" OnBeforeInternalNavigation="(arg) => arg.PreventNavigation()"></NavigationLock>
<SfBreadcrumb OverflowMode="BreadcrumbOverflowMode.None" EnableNavigation="false">
<BreadcrumbItems>
<BreadcrumbItem Text="#1" Url="/page1"></BreadcrumbItem>
<BreadcrumbItem Text="#2" Url="/page2"></BreadcrumbItem>
<BreadcrumbItem Text="#3" Url="/page3"></BreadcrumbItem>
<BreadcrumbItem Text="#4" Url="/page4"></BreadcrumbItem>
<BreadcrumbItem Text="#5" Url="/page5"></BreadcrumbItem>
</BreadcrumbItems>
</SfBreadcrumb>
The Navigationlock is preventing going to another page. On production-level there will be a confirmation-dialogue, but for a simple test, i left it out here.
The issue here is, that i'm not able to prevent the clicked breadcrumb to disappear (what is correct behaviour, if the navigationlock is not preventing the navigation).
My hottest candidate would have been the ItemClicked event, but there is no “arg.Cancel()” or simply “return false”.
The only workaround I have found is to disable the breadcrumb completly when the navigationlock is active, but that doesn't feel like a sensible solution :)
I guess its OK, that the SfBreadcrumb is not aware of the prevented Navigation, but it should be possible to configure the click-behaviour; in this case simply preventing navigation and disappearing.
Maybe this is already possible but i missed the trick - can you give me a hint in this case?
I'm currently on v26.2.7.
Hi Rene,
We have checked the reported query, and currently, we do not have the support to display all breadcrumb items when an item is clicked. In our current behavior, clicking an item causes it to disappear.
However, we have considered your requirement an improvement “Provide options to show all items while clicking the Breadcrumb" and logged an improvement report for it. You can track the status of this improvement by using the following feedback report link.
We regretfully can't start this improvement implementation immediately since we prioritized bug fixes and features that came before them in the queue for forthcoming releases. The time between releases is typically at least three months. Every release cycle, we assess all open features again during the planning phase and decide which ones to deploy based on a number of criteria, such as the product vision, technology viability, and user interest. The feedback will be moved to scheduled status with an estimated delivery period whenever we have more information to provide regarding the development of these improvements. We appreciate your patience until then.
Regards,
KeerthiKaran K V
Thank you for the reply and the estimate of when it might be implemented.
Hi Rene,
As we have already lined up some major features, we could not start this feature immediately. We will implement this support and include it in any of our upcoming releases. Please cast your vote to make it count. We will prioritize the features for every release based on demands. Until then, we appreciate your patience. Please track the status using the below feedback link.
Please let us know if you need any further assistance on this.
Regards,
KeerthiKaran K V
