predixdesignsystem / px-breadcrumbs

https://www.predix-ui.com/#/elements/px-breadcrumbs
Apache License 2.0
0 stars 2 forks source link

Error after changing selection in px-context-browser #19

Open lkvposs opened 6 years ago

lkvposs commented 6 years ago

We are using px-context-browser and px-breadcrumbs for navigation in our app. The functionality of the context browser is working as expected and each selection's path from the context browser shows up correctly in the breadcrumbs. However, making a selection directly from breadcrumbs results in an error. We are managing changes to the context on the selected-meta-changed events of both the context browser and breadcrumbs. The item's property of the context browser and breadcrumbs is bound to the same data object.

Expected behavior and actual behavior:

Expected behavior - We expect to be able to update the application's context via the breadcrumbs. Actual behavior - The new selection is displayed in the breadcrumbs, but the context is not actually updated anywhere, including in the context browser. An error is displayed in the console saying "Error: The following item could not be found in the items graph: {}".

Steps to reproduce the problem:

  1. App loads with no context selected (nothing is shown for the breadcrumbs)
  2. A user makes a context selection using the context browser
  3. The breadcrumb's path populates based on the user's context selection
  4. The user clicks on a level in the breadcrumbs that has other context options at that level
  5. The user clicks on a different context option in the breadcrumb's dropdown
  6. The displayed breadcrumbs path reflects the new context selection, but an error is thrown and the selected-meta-changed callback is never triggered

Environment (component version number, Browser (including version), operating system, hardware, etc):

component version number: 1.0.8 browser: Chrome v63.0.3239.84 OS: El Capitan v10.11.6

Screenshots (optional, but very helpful):

screen shot 2017-12-18 at 11 05 23 am

mdwragg commented 6 years ago

Hi,

Thanks for the defect - can you supply a minimal example exhibiting this issue? A glitch/codepen/jsbin etc. We need to be able to recreate this in isolation to fix it.

Thanks.