As this library doesn't use the "complete" promise from beforeNavigate, but instead uses afterNavigate to "finish" the progress-bar, it fails to take into account navigations which fails or are cancelled. I would imagine the most common occurrence of this (which is the one I ran into) is cancelling the navigation during beforeNavigate using the cancel param, which will just leave the progress-bar hanging giving an impression of a broken app
As this library doesn't use the "complete" promise from beforeNavigate, but instead uses afterNavigate to "finish" the progress-bar, it fails to take into account navigations which fails or are cancelled. I would imagine the most common occurrence of this (which is the one I ran into) is cancelling the navigation during beforeNavigate using the cancel param, which will just leave the progress-bar hanging giving an impression of a broken app