Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Learn More

Pages won't load if another tab is waiting for a slow script which is on the same website

  • 1 wótegrono
  • 5 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót juanps90

more options

If there is a tab that is waiting for slow script other tabs on the same website will be affected, even though they should not.

Test case:

1. Open a tab and run a slow script ( example: http://localhost/slow_script.php ) 2. Open another tab and run a normal script ( example: http://localhost/normal_script.php )

What should happen:

The normal script will load, the slow one will be waiting for the server to finish.

What happens:

The normal script wont start loading until the slow one finishes.

Is there any way to work around this issue?

Thanks !

If there is a tab that is waiting for slow script other tabs on the same website will be affected, even though they should not. Test case: 1. Open a tab and run a slow script ( example: http://localhost/slow_script.php ) 2. Open another tab and run a normal script ( example: http://localhost/normal_script.php ) What should happen: The normal script will load, the slow one will be waiting for the server to finish. What happens: The normal script wont start loading until the slow one finishes. Is there any way to work around this issue? Thanks !

Wšykne wótegrona (1)

more options

I have to add that the delay is not caused by the server itself. Running two web browsers or using multiple computers does the trick.

Using a simple sleep function to make the script take longer seems enough to reproduce this bug. There is no need to consume actual resources on the web server.