Peter Burns

Conceptually this is pretty straightforward I think, the main open questions are around how best to plumb the information that describes the nature of the most recent navigation through the...

Good point! We could definitely give a better default url space regex for this use case. We still want to match links to the current page's path but different query...

This is a nice feature to have, especially for a reusable routable element. The tricky thing here is that this requires something of global knowledge. You need to know how...

@robdodson This is true. Link generation getting significantly harder appears to be part of the trade off for modular and decentralized routing.

There is! app-route and app-location automatically add entries to the browser's history. You can programmatically go back using native apis like `window.history.back()` and `window.history.go(-1)`. Docs here: https://developer.mozilla.org/en-US/docs/Web/API/Window/history

Can you clarify your first point? Are you talking about something firing popstate events? Something listening for them? iron-location and thus app-location listens for `popstate` events and responds appropriately. As...

That's awesome! That seems like the right approach to me @CaptainCodeman.

We haven't proved one out enough to have a recommended strategy, but it may be very straightforward. e.g. If you're not using the hash as the path then you could...

@cdata That's clever. I like that the reverse function to generate the hash for a node is similarly straightforward. Advantages: - simple and easy to understand - polymer-agnostic, cuts with...

I'm not sure if that would be enough for this use case. I think that you want to configure the loading promise on the route that's being navigated _to_, rather...