Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why is Safari restricted from using the service? #33

Open
RA80533 opened this issue Mar 20, 2021 · 1 comment
Open

Why is Safari restricted from using the service? #33

RA80533 opened this issue Mar 20, 2021 · 1 comment

Comments

@RA80533
Copy link

RA80533 commented Mar 20, 2021

It appears that Safari is functionally compatible with the website once the Safari-specific restrictions are removed. Is there a particular reason why the browser is prevented from using the service?

Safari 14.0.3

@robertodauria
Copy link
Contributor

There seems to be a bug in the Webkit implementation of websockets preventing the message scaling algorithm to work properly, which results in upload measurements failing on some combinations of machine speed + connection speed. Further details: m-lab/ndt7-js#19 (comment)

There is also a different issue in the download measurement, so that it never reports more than ~500 Mb/s in our testing -- only on Safari.

While it would appear that the measurement is running just fine on Safari (and in most cases, i.e. < 500Mb/s, this is probably true), some percentage of measurements done on Safari will either fail while showing unreasonably high upload rate to the user (first bug), or under-report the download speed (second bug).

We decided to disable it until either we have a good workaround for these two issues, or they are fixed in Safari.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants