Vaadin router should follow standard navigation if it cannot find a route

[pietrorea]

Vaadin router should follow standard navigation if it cannot find a route

[platosha]

Hi @pietrorea, thanks for filing this. Good idea for an enhancement, I think.

Ideally, the router’s path matching was sync, we could avoid event.preventDefault() for the click event if the path matching did not find a good route, so that the browser handling continues naturally handling the link click with standard navigation (not possible today as the path matching is async).

Sounds good to make it an opt-in behaviour also.

Related tip, if each Vaadin router in your case is only handling a specific path-prefixed scope, consider using the baseUrl option. This prevents Vaadin router from handling link clicks outside the path-prefixed scope (e. g., for <a href="/admin">Admin app</a> link it would use standard navigation if the router’s baseUrl is set to /app).