Alexander Harding

This may be blocked by https://bugs.chromium.org/p/chromium/issues/detail?id=1026287 - I'm not quite sure

For those that are still having issues binding Cleave to `this.$refs.input` (or whatever) -- I found a surprisingly easy fix that hasn't been documented yet: `v-model.lazy="foo"` The `.lazy` modifier makes...

I just wanted to say that I took a step back to look at this problem. To me, this isn't a problem with the Vue router. Routes should be immutable...

Just for an example of handling the 404s, etc of something, this is how I handle it: Say I have a comment that I can get to at `mysite.com/comments/:id`. I...

@giolf Yes, I do realize it's a bit of scaffolding. I'm not sure how it could be made simpler, but I'd love if someone could make a solution and share...

That's good to hear. I look forward to your solution! I guess what I'm trying to get at is that the ability for the view to depart the route and...

That would definitely work :) I'd definitely like to see an example (I'm a learn-by-example guy), but sounds promising. It would be great to have a page on the router's...

@micbenner The major problem with this is that it makes the route/state relationship non-determinable. Mutating the state matching regardless of the current URL. In other words, for a given route,...

@signorbusi thanks, that worked great for me! I just had to update it to have a `z-index` higher than my header (that was being clicked through to). For me- ```ts...

Just an update. one of the drawbacks of this method is the page will not be interactable for clicking for about a second after closed. Kinda annoying :/ Looking for...