SilentCatDev
SilentCatDev
> @patrikheinonen that issue seems to be a different problem. > > I don't have a update for this issue, and no one is actively working on this. Something that...
> > For eg: we can have: GoAction, PushAction, NoAction. I think that is enough to handle this issue > > If we want to go this route, we can...
> Hi @SilentCatD > > I would replace it if we implement this. I don't think this add much boilerplate and can achieve everything `redirect` can do. Is there a...
Can we also consider the importance of seeing the requested route's navigation method (push, go, ....) For example, the requested route must be navigated by the go method. But the...
> I believe the void redirect(context, state, router) is simpler to understand. > > We would simply use the same API we already use to navigate. No extra booleans, "stopProgating"...
any update on this? I can try the way [FWeissenb](https://github.com/FWeissenb) suggest and it works, though it felt improper
Any update on this?
Hi, I just want to add a workaround that would atleast have visual representation of keyboard navigation accessibility. You can put a WidgetSpan which will render a Container() wrapped in...