Closed colinjlacy closed 6 years ago
damn
There's a bug in the Google analyzer that builds our API pages, but the description for that event should read: This event is fired whenever a click occurs - from a top path item, or dropdown item - that changes the context. The new context is attached as 'item'
gotcha. thank you sir!
Expected behavior and actual behavior:
When I'm using this component, I have to pass in an array of items for the
selected-route
in order for the breadcrumbs to display as expected. Similarly, I have to listen for emits of theselected-changed
event to know when a user has interacted with the component, and to route them accordingly. I'm currently seeing aselected-changed
event being emitted for both cases - when the binding data indicating theselected-route
changes, and when the user clicks on an item. I would expect to see two different events - specifically one that is unique for user-based interaction, similar to what is done in thepx-app-nav
with thepx-app-nav-item-tapped
event.