Jason Miller

Hi @apostololeg! I think we could actually just remove the bubbling prevention. `preact-router` is only replacing the default behavior, so it should really only be preventing default, not bubbling. Want...

Agreed! It would be nice if the URL bubbled down for sure. The only workaround I'm aware of right now is to pass a custom history to Router to tell...

Awesome! Let's keep this issue open to see if we can make it work without the custom history.

`.listen()` can just be an empty function - SSR is a single-pass render, so listening can't respond anyway: ```js const customHistory = { location: { pathname: "/foo" }, listen: ()...

Ah, good catch. I think right now preact-router is entirely case-sensitive, but the browser is not.

I mentioned it on slack, but preact-router doesn't have any knowledge of async components - that's a preact-cli thing the router can't see.

I'm going to cross-post this from Slack for others - here are two options for handling `preact-cli` async component loading errors using preact-router. ## Option 1: Simple You can use...

heh - yeah that's a much better solution @peterbe, ~I'll update~ I updated the code.

Hi @thadeu - I'm not sure I quite follow what's being asked for here. There's already a `componentWillUnmount()` method for this.

Ah neat solution @studentIvan - I hadn't thought of injecting into History, haha.