Jump to content

Beta Download hangs up with older Safari 13.1.2 - OK with Classic test


Pgoodwin1

Recommended Posts

@CA3LENot that it's all that important, but my old iMac OS is still v10.13.6 High Sierra and can't be updated. With Beta OFF, the Download test runs fine though.

 

Probably not that many people coming to your site with a 14 year old computer, so I wouldn't blame you if you paid no attention to this issue. I normally run your tests with my fairly new iPad. Just thought you might want to know in case there was an issue that might affect versions newer than mine but not the latest. I get plenty of other websites on this computer with issues because this Safari is so out-of-date. 

 

Like I said, I don't really need you to fix this. The computer is so old that it can't run at the full speed that my ISP allows. My good results on this machine are about 220 Mbps, and on my iPad I get 320 Mbps on the 300 Mbps Spectrum plan. So I don't use this computer any more to assess my Internet speed and delay times.

 

Right after I hit the Download button or choose a Manual size test, it goes here and just sits. 

 

Beta Hangup Safari 13.1.2.png

Link to comment
Share on other sites

Not too sure why it's showing the post 7 hours old on the forum index, I'll look into that.

 

As for the beta not loading on v10.13.6 High Sierra.  I've had to make special accommodations for older browsers with every beta release.

 

I'll do some tests myself with Safari 13 and make the changes needed.  It will probably just have to fail over to the previous version because the browser may not have capabilities needed.  But if that's the case I'll have it show a notice to the client and disallow setting the beta. ...sometimes, I just need to call a method a little differently or reform some functions to make it work.

 

My wife's laptop (2015 Macbook) isn't getting updates anymore, for a long time it was stuck on the old version of Safari... then all of a sudden it gave an update the other day.  To 16.6.1 -- the version on my 2020 iMac is 17.5.

 

Still searching for official word from Apple on this.  See if you maybe have an update... long shot.

Link to comment
Share on other sites

I compiled chart.js into ES5 javascript and added a ResizeObserver polyfill (adding a newer JS feature to an older browser, filling the gap) and am able load the beta is Safari 13.1.2 now with no issues.

 

495.2 Mbps [61.9 MB/s] | Downloaded 200 MB Linear in 3.23 seconds
Pre-Test: 520 Mbps [65 MB/s] | 106.7 MB in 1.64 seconds
Download Graph: [560,552,544,512,488,496,432,480,488,504,504,512]
Test Latency 44 ms Avg - 16 ms Min
Latency Graph: [117,117,66,16,18,16,110,19,17,16,129,17,16,24,19,16,16]
User: CA3LE | CompID: 6532027578876 | Host: Comcast Cable | Locale: co.testmy.net
User Agent: Mozilla/5.0 Macintosh; Intel Mac OS X 10_13_6 AppleWebKit/605.1.15 KHTML, like Gecko Version/13.1.2 Safari/605.1.15
Graph & Validate: https://testmy.net/x/tmn?resultID=8IZxw75l0

 

40 Mbps [5 MB/s] | Uploaded 24.8 MB Linear in 4.96 seconds
Pre-Test: 40 Mbps [5 MB/s] | 10 MB in 2 seconds
Upload Graph: [44.8,40.8,44,42.4,43.2,41.6,40.8,41.6,40.8,41.6,41.6,42.4]
Test Latency 39 ms Avg - 11 ms Min
Latency Graph: [51,56,42,12,12,50,11,44,43,44,48,51]
User: CA3LE | CompID: 6532027578876 | Host: Comcast Cable | Locale: co.testmy.net
User Agent: Mozilla/5.0 Macintosh; Intel Mac OS X 10_13_6 AppleWebKit/605.1.15 KHTML, like Gecko Version/13.1.2 Safari/605.1.15
Graph & Validate: https://testmy.net/x/tmn?resultID=x69j8nxpt

 

Hoststats and DB search charts also rely on this same resource.  Charts are working across all pages on my iMac running a fresh install of High Sierra.

 

My super old iPad, not so much.  That's running Safari 10.  I thought this would have worked... there may be another polyfill I need.  But it's really hard to debug that one because I can't get it to connect in dev mode (so I can see what's really happening in the console).  Maybe if I reset the device.  But then I go to use the internet in general on that thing and pretty much all sites are broken in some way.  May be time for that to retire.

 

So this won't fix all cases but it should bridge the gap for many.  It's basically been translated into language old browsers can understand.

 

There are ways to polyfill the entire modern js framework... but how much of a payload do I want to send?  Answer: As little as possible.  It may not be worth it to make it work for every single browser.  Especially since I have a legacy version of tests and charts that work in that scenario... I just need to give it instructions to serve that client a little different.  Which isn't ideal but it will work.

 

Please let me know if it's working for you now.

 

Link to comment
Share on other sites

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...