Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Browser navigation in a view does not work when using wbRouterLink with default target (self) #409

Open
k-genov opened this issue Feb 6, 2023 · 0 comments
Projects

Comments

@k-genov
Copy link
Contributor

k-genov commented Feb 6, 2023

Describe the bug

When using the wbRouterLink directive with default configuration (wbRouterLinkExtras with target self) the view being replaced remains blank (empty) if e.g. browser back navigation is used after clicking on the link

To Reproduce

Steps to reproduce the behavior:

  1. Create empty angular app
  2. Create a standalone home component (e.g. desktop) with a route navigation (e.g. <a wbRouterLink="/customers">Customers</a>). When clicked this will open (view.1:customers)
  3. Create another standalone home component (the customers) ( <a [wbRouterLink]="['/customers', 1]">first lastname</a>). When clicked this will replace the content of view with (view.1:customers/1)
  4. Create the third standalone component customer.
  5. When on the customer detail page click browser back - view remains empty with url (view.1:customers). Click again on browser forward. The view is still empty.

Expected behavior

Browser navigation should work when view content is replaced.

Screenshots

If applicable, add screenshots to help explain your problem.
http://localhost:4200/#/(view.1:customers)?parts=eyJyb290Ijp7InZpZXdJZHMiOlsidmlldy4xIl0sInBhcnRJZCI6Ijk4ODVlNWZjLTA2YTAtNDVkNi04MGFiLTBkMmQwZmIzYWY1NyIsImFjdGl2ZVZpZXdJZCI6InZpZXcuMSJ9LCJhY3RpdmVQYXJ0SWQiOiI5ODg1ZTVmYy0wNmEwLTQ1ZDYtODBhYi0wZDJkMGZiM2FmNTciLCJ1dWlkIjoiNmJjOGU0ZmUtNDExYS00OTM3LTlmNDYtNGMwNDhkODg4YWYyIn0%3D
image

Environment

Please complete the following information:

  • SCION Workbench version: 14.0.0-beta.9
  • SCION Workbench Client version: 1.0.0-beta.16
  • Angular version: 14.2.0
  • Browser: Edge 109.0.1518.70
  • OS: Windows 10
  • Device: [e.g. Desktop, Smartphone]

Additional context

Add any other context about the problem here.

@k-genov k-genov added this to Triage in SCION via automation Feb 6, 2023
@k-genov k-genov moved this from Triage to Backlog Workbench in SCION Feb 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
SCION
  
Backlog Workbench
Development

No branches or pull requests

1 participant