Supported Web Browser?

[startergo]

Weird. Maybe i just got lucky. Once in awhile i have to hit refresh if a page stops loading, but otherwise surf and epiphany both work well enough for the few "modern" pages i need them for. I just use them for that sole purpose, not for general use. It sure beats waiting for a VM to boot Linux to use current firefox or chromium.

Do you have these spinning circles on some github pages in Interweb on SL?

 

[startergo]

The only way to get around this (In Chrome) is to Inspect the element and copy outer HTTP and launch it separately.
For instance all Assets appear with loading spinners and if I dig the actual HTTP I browse to this:

Otherwise I would only get the rotating element spinner:

 

[f54da]

What version of chromium is that? Seems pretty old considering it has pre-macviews icons. It probably doesn't support whatever new javascript syntax that github is using to dynamically fetch things.

 

[startergo]

What version of chromium is that? Seems pretty old considering it has pre-macviews icons. It probably doesn't support whatever new javascript syntax that github is using to dynamically fetch things.

I believe it is 49. Latest to support SL. Firefox, Safari and Chrome browsers all behave the same way.

 

[wicknix]

Do you have these spinning circles on some github pages in Interweb on SL?

Yep. It happens to all older browsers now. Thank Microsoft for ruining GitHub. Yeah, just remove /tag/ in release urls and replace with /expanded_assets/ to work around it (for now).

 

[f54da]

49 is ancient in the everchanging world of web development. I'm guessing it's probably supporting only at most ecma2015 or something, and so it's breaking on newer syntax.

Since JS transpilers exist it's theoretically possible to have a proxy that transpiles JS to older syntax on the fly as it grabs the scripts, but this is not worth implementing probably since other things will break too. Css for instance, move to webassembly, etc.

 

[startergo]

Yep. It happens to all older browsers now. Thank Microsoft for ruining GitHub. Yeah, just remove /tag/ in release urls and replace with /expanded_assets/ to work around it (for now).

in EC it still happens in Safari, but Chromium legacy is working fine.

 

[wicknix]

Because chromium legacy is current chromium 109.

 

[f54da]

This might be useful, claims to polyfill webcomponent support on older firefox

GitHub - JustOff/github-wc-polyfill: Ensure that all GitHub and GitLab scripts required for UXP and SeaMonkey are loaded correctly

Ensure that all GitHub and GitLab scripts required for UXP and SeaMonkey are loaded correctly - JustOff/github-wc-polyfill

github.com

Edit: https://github.com/martok/palefill is newer version