Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Weird navigation behaviour for angular app

  • 1 resposta
  • 0 têm este problema
  • 118 visualizações
  • Última resposta por Grimaldus12

more options

I am developing an Angular App which uses a web-socket for backend communication. Interestingly, whenever I open the app in firefox (localhost:4200) the navigation bar breaks. I can't change the URL manually anymore, but every time I submit a changed URL it first redirects to the specified page but then immediately overwrites the navigation with the previous URL.

Example:

  1. Call http://localhost:4200/
  2. Sometimes the first additional navigation works, but afterwards all manual changes using the address bar will result in the behavior shown in the below image.

Steps I have taken to narrow down the error cause:

  • I ruled out a device specific issue, since the problem occurs on both my machines.
  • It is specific to firefox, since both edge and chrome work perfectly fine
  • I don't think it is related to the angular router and the way I use it, since it would be quite weird that a website could force a user to stay on it.
  • It is not related to the Angular CLI since the error also occurs when I deploy the angular with nginx.

I haven't found any hints on what might cause this behavior or even how to debug the network traffic further to maybe see what is causing the navigation override.

I am developing an Angular App which uses a web-socket for backend communication. Interestingly, whenever I open the app in firefox (localhost:4200) the navigation bar breaks. I can't change the URL manually anymore, but every time I submit a changed URL it first redirects to the specified page but then immediately overwrites the navigation with the previous URL. Example: # Call http://localhost:4200/ # Sometimes the first additional navigation works, but afterwards all manual changes using the address bar will result in the behavior shown in the below image. Steps I have taken to narrow down the error cause: * I ruled out a device specific issue, since the problem occurs on both my machines. * It is specific to firefox, since both edge and chrome work perfectly fine * I don't think it is related to the angular router and the way I use it, since it would be quite weird that a website could force a user to stay on it. * It is not related to the Angular CLI since the error also occurs when I deploy the angular with nginx. I haven't found any hints on what might cause this behavior or even how to debug the network traffic further to maybe see what is causing the navigation override.
Capturas de ecrã anexadas

Solução escolhida

Issue resolved itself. I was reloading the window when loosing connection to websocket which obviously happened when changing the window url/location so an additional reload was triggered.

Ler esta resposta no contexto 👍 0

Todas as respostas (1)

more options

Solução escolhida

Issue resolved itself. I was reloading the window when loosing connection to websocket which obviously happened when changing the window url/location so an additional reload was triggered.