We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

تلاش سپورٹ

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

مزید سیکھیں

اس تھریڈ کو آرکائیوکیا گیا تھا۔ اگر آپ کو مدد کی ضرورت ہو تو براہ مہربانی نیا سوال پوچھیں۔

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

  • 1 جواب دیں
  • 5 میں یہ مسئلہ ہے
  • 1 دیکھیں
  • آخری جواب بذریعہ juanps90

juanps90
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 !

تمام جوابات (1)

juanps90
juanps90 سوال کا مالک
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.